[ynniv]

Device specific extra pixels were a bad idea. Further modifying web design standards to account for them is making the problem ten times as bad. Where's the CSS declaration that tells Safari to make those pixels black so no one has to care about this? Unplanned sections of background color around your header bar is not "displaying existing websites beautifully".

[SiVal]

Whether or not Apple does this, others will. The web platform needs a well-considered generic approach to non-rectangular displays to support a widening array of devices: watches, medical devices, decorative displays, industrial controls, e-paper-type displays wrapped around a pipe, etc. They could have multiple panels of different sizes, have holes in the middle (not just the edge), be extremely curved, or whatever.

I'm fine with learning new, standard techniques for dealing with a broadening range of opportunities, but it's annoying to have to learn and incorporate Apple-only technologies in my web apps. But if the standard platform doesn't have a solution, Apple will solve it themselves.

[alwillis]

Apple is using W3C blessed standards:

* https://github.com/w3c/csswg-drafts/issues/1693#issuecomment...

* https://drafts.csswg.org/css-values/#calc-notation

* https://www.w3.org/TR/css-round-display-1/#viewport-fit-desc... (Apple is doing the meta tag version of the @viewport descriptor)

[bfred_it]

> Apple is doing the meta tag version of the @viewport descriptor

Which means they are in fact NOT using W3C blessed standards.

[om2]

> Where's the CSS declaration that tells Safari to make those pixels black so no one has to care about this?

  body { background-color: black; }

[Walf]

I will definitely be implementing this.