preferredVerticalBarBehavior guidance

For the preferredVerticalBarBehavior, docs say to "treat it as a stable choice: avoid changing it frequently as the user navigates, and don’t toggle it for a single view controller as a function of that view’s state. To hide the bars and status bar on a given screen rather than change the layout, use the visibility APIs instead."

I'm wondering if that's supposed to apply to size class changes as well. On the simulator, Safari displays the vertical bar in compact widths but seems to set it to .disabled when in regular width (ie, the bar is in horizontal position when the app is displaying fullscreen on the inner screens). Is it OK to follow that example in our own apps?

In Safari, the tabs UI benefits from the additional horizontal space gained by setting preferredVerticalBarBehavior to disabled, as the tabs are dynamic content that are stacked horizontally.

In general, the advice from the docs still stands. You should really only reach for disabling the vertical bar if your use case is similar enough to warrant diverging the UI between compact and regular horizontal size classes.

For example, see how the vertical bar in Notes allows for more room for content at the top (when scrolled, this screenshot is scrolled to the top):

preferredVerticalBarBehavior guidance
 
 
Q