You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iPhone X or later always display a bar-thing that brings up the App Switcher on the screen. On IITC mobile, this causes the status bar to be partially obstructed (screenshot is on iPhone 12mini):
I believe the official Apple design guideline on this sort of issue is: "just leave more space out". Compare the iPhone X-and-later and home-button-iphone screenshots in https://support.apple.com/en-us/118408. The Weather and Safari apps clearly have a taller bottom-bar to compensate. (Maybe a real designer can link me the relevant section in the iOS HIG; I'm not reading through that stuff.)
This is arguably a stronger usability limit than the related #13, because it affects way more iPhone models. Either way, the cause and fix (from the Apple-guideline perspective) is the same: add bottom padding.
In #13 (comment) you argued that it "should be an IITC issue", but based on the Weather and Safari examples (118408), I believe it's more of an issue of the browser making use of space that isn't really there for it to use.
I've thought a little more about view area. There are cases where it's acceptable for content to display in the bottom, analogous to the Settings screenshot from 118408: lists of messages, portal detail pages, whatnot. The one case that it shouldn't display is when it shows critical information from the status bar.
So instead of altering the Swift part to change the webview dimensions, CSS might just be best. fix-ios-notch.user.js already uses safe-area-inset-bottom to decide how much padding-bottom to use to steer of the home bar. I really want to push for it to be a default, or at least a pre-bundled plugin.
You know what, I should just comment in #13 and say I want the plugin to be included by default. You seem aware of the notch interaction; whatever that opposing developer said should just be ignored.
Well, too late. You already have received an annoying notification email, might as well keep it here.
The text was updated successfully, but these errors were encountered:
iPhone X or later always display a bar-thing that brings up the App Switcher on the screen. On IITC mobile, this causes the status bar to be partially obstructed (screenshot is on iPhone 12mini):
I believe the official Apple design guideline on this sort of issue is: "just leave more space out". Compare the iPhone X-and-later and home-button-iphone screenshots in https://support.apple.com/en-us/118408. The Weather and Safari apps clearly have a taller bottom-bar to compensate. (Maybe a real designer can link me the relevant section in the iOS HIG; I'm not reading through that stuff.)
This is arguably a stronger usability limit than the related #13, because it affects way more iPhone models. Either way, the cause and fix (from the Apple-guideline perspective) is the same: add bottom padding.
In #13 (comment) you argued that it "should be an IITC issue", but based on the Weather and Safari examples (118408), I believe it's more of an issue of the browser making use of space that isn't really there for it to use.
I've thought a little more about view area. There are cases where it's acceptable for content to display in the bottom, analogous to the Settings screenshot from 118408: lists of messages, portal detail pages, whatnot. The one case that it shouldn't display is when it shows critical information from the status bar.
So instead of altering the Swift part to change the webview dimensions, CSS might just be best. fix-ios-notch.user.js already uses safe-area-inset-bottom to decide how much padding-bottom to use to steer of the home bar. I really want to push for it to be a default, or at least a pre-bundled plugin.
You know what, I should just comment in #13 and say I want the plugin to be included by default. You seem aware of the notch interaction; whatever that opposing developer said should just be ignored.
Well, too late. You already have received an annoying notification email, might as well keep it here.
The text was updated successfully, but these errors were encountered: