Generically speaking there are already are odd screens, and again, in the next couple years we will see how wide spread that gets. Those elements bumping in and out on scroll? Sucks, is ugly and horrible for users, our audience.Īnd to have to custom code around every possible device screen’s possible differences in shape based on orientation? Bah, you are wasting your time and money or your employers or your clients’.Ĭonsider how our code will look if there are 300 different screen types we have to code for?
Odd shaped screens are not guaranteed to require custom programming. The viewport-fit=cover seems like a good way to solve this IMO. Vojta Stavik September 13, The change is coming and we developers have to embrace it. I think I’ve fixed the notch issue in landscape 🍾 #iphoneX /hGytyO3DRV If you’re going to cover that viewport, it’s likely you’ll have to get a little clever to avoid hidden content! You can see just how bad it is in this video clip:įortunately also an easy fix, as the viewport-fit=cover addition to the meta viewport tag fixes it. As you scroll up, it will again fall down below the status bar (leaving an awkward gap where content shows through in the 20px gap). As you scroll down, it will move up behind the status bar. This means that if you have a header bar that is a fixed position element with top: 0, it will initially render 20px below the top of the screen: aligned to the bottom of the status bar. Where iOS 11 differs from earlier versions is that the webview content now respects the safe areas. There is another awkward situation with the notch, the safe area, and fixed positioning. ( Update: when the iPhone X first came out, it used constant() instead of env(), but as of 11.2, constant() has been removed in favor of the standardized env()). padding: env(safe-area-inset-top) env(safe-area-inset-right) env(safe-area-inset-bottom) env(safe-area-inset-left) I added the following to the main container on the website. This can be added to margin, padding, or absolute position values such a top or left. In order to handle any adjustment that may be required iOS 11’s version of Safari includes some constants that can be used when viewport-fit=cover is being used.
There is some new CSS that helps you accommodate for that. Then it’s on you to account for any overlapping that normally would have been handled by the safe area. Or, expand the website the whole area (notch be damned), you can add viewport-fit=cover to your meta viewport tag. It’s not much of a trick to remove it though, a background-color on the body will do. The result is some awkward situations for screen design, like constraining websites to a “safe area” and having white bars on the edges. Apple’s iPhone X has a screen that covers the entire face of the phone, save for a “notch” to make space for a camera and other various components.
0 kommentar(er)
