Closed MojtabaHs closed 3 years ago
tableView.contentInsetAdjustmentBehavior = .never
No luck @wtmoose. I've tested that before, also for the navigation controller, also for a simple view controller, all with no luck
It is not the tableView
's behavior.
You can see the inset even if you add a simple ViewController.
302px ≠ 350px
Seems to work for me:
I had to turn off "Under top bars" on the view controller since turning off automatic insets removes the top inset as well.
In the demo app, go to View Controller | Bottom Card
Here's an example with a simple view controller. Just don't constrain content to the safe area guides. This seems trivial, so maybe I'm not understanding your use case?
Strange! it is working on both examples you sent but not on the clone of the master.
Can you please share a commit so I can see what are you changing exactly that I'm missing?
There's no commit. You can copy the files into your project folder on top of the head of master
and you'll see the diffs.
I know we can ignore the safe area inset since v8.0.4. but the content still cares about the safe area:
Note that little inset below item 3? That is exactly the bottom safe area and it is visible only if the container passed the minimum inset (and not respecting the safe area)
So how can I ignore the safe area for the content too?