Re:WebKit Features in Safari 16.1
by nozzlegear on Monday October 24, 2022 @02:59PM
(#33320856)
Why does it matter if they're first to implement a standard?
[ Parent
| on HN ]
Re:WebKit Features in Safari 16.1
by encryptluks2 on Monday October 24, 2022 @03:33PM
(#33321373)
Because Safari is gatekeeping not innovating and implementing W3C standards.
What are they gatekeeping here?
Re:WebKit Features in Safari 16.1
by encryptluks2 on Monday October 24, 2022 @05:54PM
(#33323144)
Web standards and features. I assume you haven't heard of them intentionally limiting PWAs?
Huh, I didn’t realize that there was a “web standards and features” standard, or a PWA specification - could you provide the urls?
Or alternatively actually answer the question like an adult rather than parroting the standard Apple hates the web nonsense.
False.
In case nobody noticed, the WebKit team kicked ass by shipping a ton of new features this year:
* dialog element
* lazy loading
* inert
* :has() pseudo-class
* new viewport units
* Cascade Layers
* focus visible
* accent color
* appearance
* font palettes for color fonts
* BroadcastChannel
* Web Locks API
* File System Access API
* enhancements to WebAssembly
* support for Display-P3 in canvas
* additions to COOP and COEP
* container queries
* subgrid
* web push
* shared workers
* CSS Offset Path
* AVIF
* Passkeys