[killwhitey]

>Mobile Safari can easily handle, say, a Photos.app-like interface with a translucent navigation bar, native-like swipe gestures and smooth animations. Chrome handles none of this. No position:sticky, no backdrop-filter, no scroll-snap-type

It's interesting that the things he lists as Safari having only work via a -webkit vendor prefix.

[om2]

These features are all standards track but not final, much like the features that people praise Chrome for having that are not in Safari. Chrome's policy is not to prefix when they ship a feature to everyone, even if the spec is not finalized yet. Safari's policy has been to prefix in such a situation but there is consideration of changing it.