Apple Broke the Website, Again
-
@boomzilla said in UI Bites:
Make a FREE!!!11 thread yourself if you think it's an actual NodeBB/WTDWTF bug.
On iPhone X and above, on iOS 11.2 and above, the virtual home button overlaps with the post-in-thread scrubber, and as a result the scrubber can be illegible and can't be used. @levicki has screenshots in the UI Bites thread.
To avoid this issue, the site needs some additional CSS to move the scrubber
3pxenv(safe-area-inset-bottom)up. Because this stuff is ridiculously nonstandard, it needs an in-CSS feature test and a bunch of math. The Webkit blog has some suggestions.
-
Quick and dirty not comprehensively tested CSS fix:
.topic .pagination-block { padding-bottom: env(safe-area-inset-bottom); }Screenshot of above fix on iOS simulator over RDC
Could be applied as custom CSS for affected users or as a WTDWTF customization until the issue is fixed officially (and we update to said fixed version).
-
"We're a big company and we decided to do something utterly weird with our hardware, and now everyone has to adjust their websites to work with our madness."
-
@PleegWat said in Apple Broke the Website, Again:
"We're a big company and we decided to do something utterly weird with our hardware, and now everyone has to adjust their websites to work with our madness."
Except that if the browser developers (including Safari) followed the iOS guidelines, the websites wouldn't need to.
-
@loopback0 That would probably reduce the number of website pixels, which reduces how useful the pixels are?
-
@PleegWat said in Apple Broke the Website, Again:
@loopback0 That would probably reduce the number of website pixels, which reduces how useful the pixels are?
What difference does it make if the website shows a blank space at the bottom or if safari shows a blank space at the bottom?
-
@topspin Because the website could choose those blank pixels. In @ChaosTheEternal's demo, the coloration of the
pagination-blockextends into the area of the home button for greater visibility. If the browser did that, it would be white, not pagination-block-colored. Apparently some "web" designers care deeply about such things.
-
@TwelveBaud Frankly, IMO, such things should work 'by default' with special behaviour triggered when the developer enables it. No clue what shape that should take, but obscuring part of the page is a bad default.
