MDN-Browser-Compatibility-Report-2020

Web developer quotes A sample of the 229 free-form survey responses relating to Safari:

Safari/WebKit lagging behind in implementing standards. Not just Chromium flights of fancy, but basic, super useful stuff like MediaRecorder. Browser vendors choosing to just not implement parts of specifications. I have three examples of this: 1) Safari desktop does not support type="date" on the < input> element on desktop though Safari iOS has support for this attribute. 2) Safari has decided to not implement autonomous custom elements 3) Safari does not support the Web Push API making PWAs unattractive on a major mobile platform

Safari, particularly the iOS version.

New feature adoption speed, e.g. WebP is adopted well apart from Safari and Safari iOS, could anything be done to introduce such things faster?

Safari lagging behind and not really supporting PWAs.

One interview participant followed up on email on a specific issue they had encountered:

I found a little function that is called isApple() - designed expressly to run before any calls to the "screen" object, because even though said object has been around for years, it turns out JavaScript just breaks in unpredictable ways if you call into screen properties that don't play nice with either Safari (or iOS).

After investigating, a CSSOM View spec bug was filed for this: ​ should screen.width and screen.height reflect orientation?

Made with FlippingBook - professional solution for displaying marketing and sales documents online