Where do scroll indicators go on iPhone Duo?

Question

Created 2d

Replies 2

Boosts 2

Participants 1

In the process of updating an app for the iPhone Duo, I initially changed scroll/collection view leading/trailing to use the safe area. This puts the scroll indicators "inside" the side navigation bar:

Screenshot 2026-09-27 at 12.29.46 PM.png

But looking at both Safari and Settings, the scroll indicators are placed "outside" the navigation bar:

Screenshot 2026-09-28 at 10.26.50 AM.png

This leads to a couple of questions:

Is the "outside" placement correct for a view with scrolling content?
Is there a way to achieve this without reorganizing the scroll view content?

The only solution I've found is to place a new container view inside a scroll view that uses the superview as its edge constraints. The container view gets placed using safe areas.

If there's an easier way, I'd love to know what it is.

Answer 1

chockenberry OP

2d

I think I might have answered my own question. When I encountered a collection view in my view hierarchy, I realized that adding a container view was intractable: the only views to modify are cells.

It then occurred to me that I really want to adjust content inset, so I tried this:

scrollingView.contentInset = view.safeAreaInsets

That leaves the scroll indicators at the view edges and gets my content inside the safe area.

Again, I'd like confirmation that this is the correct approach. And now I'm also wondering why this isn't the default behavior or something that can be modified in a storyboard.

Any additional information would be greatly appreciated.

Answer 2

chockenberry OP

4h

My confusion about automatic safe area insets was due to a single dropdown in a collection view's storyboard: Screenshot 2026-09-30 at 10.25.51 AM.png

The storyboard was using "Content Inset", which I'm thinking might be a default value. Everything works fine after changing the dropdown to "Safe Area" (and a sectionInsetReference="safeArea" attribute is added to the storyboard object graph).

This setting also led me to believe that table views didn't handle the situation automatically (they do).

It seems to me that "Safe Area" is a better default these days - there are probably compatibility issues I'm not aware of, but folks moving their storyboards to the Duo will likely hit this issue and be confused just like I was.