Andreas demoed these ideas yesterday. Proper ambient badging and a way of getting at URLs even if a progressive web app is running in fullscreen or standalone mode. Great stuff!
Phew! Alex seems to have calmed down. He’s responding to my concerns about exposing URLs in progressive web apps, but thankfully without the absolutist rhetoric or insults. Progress!
‘Sfunny, I’d been meaning to write a blog post on exactly this topic, but Tyler says it all …and that’s before Apple’s scandalous shenanigans.
These updated definitions makes sense to me:
- Newly available. The feature is marked as interoperable from the day the last core browser implements it. It marks the moment when developers can start getting excited and learning about a feature.
- Widely available. The feature is marked as having wider support thirty months or 2.5 years later. It marks the moment when it’s safe to start using a feature without explicit cross-browser compatibility knowledge.
Firefox as the asphyxiating canary in the coalmine of the web.
There is a crack, a crack in everything. That’s how the light gets in.
Something about a browser that grinds your gears? Share it!
Apple’s policy of locking browser updates to operating system updates is bad for the web and bad for the planet.
As mobile and desktop operating systems converge, Apple’s hypocritical browser policy becomes clearer and clearer.
Different browser vendors have different priorities.
