[jpttsn]

Honest question: Do we have any scroll vs. marquee type situations today?

Because (Unpopular): I believe the standard should primarily cover how the overlapping functionality works, and refrain from limiting or prescribing the extent of functionality.

Comparing: If I build a HTTP API, I don’t have to support the DELETE verb for any endpoints. I can support ENCHANT if I want magic that other servers don’t have. But if I use GET, the endpoint handler should be idempotent. That’s the kind of standard I appreciate.

I don’t see any realistic win-win otherwise. Either you hold Chrome back from implementing new crap, or you force Safari to implement stuff they don’t want to. The efficient number of browser vendors seems to be small, so I think the standard body has just overplayed it’s hand.

[jefftk]

> Because (Unpopular): I believe the standard should primarily cover how the overlapping functionality works, and refrain from limiting or prescribing the extent of functionality ... the standard body has just overplayed it’s hand.

But that is how web standards work already? Vendors are not prohibited from adding additional functionality.

[jpttsn]

A lot of comments say Safari is not implementing web standards, by virtue of not implementing e.g. push notifications.

[jefftk]

Those comments are correct: there are many web standards that Safari has either decided not to implement, or has not gotten around to yet. A browser doesn't have to implement a new feature just because it has been standardized.