4 ms·
This is a good point, but I do feel you're missing a step, and it's one open standards folks sort of gloss over because it's kind of icky. A feature doesn't dir
by munificent 7y ago
This is a good point, but I do feel you're missing a step, and it's one open standards folks sort of gloss over because it's kind of icky. A feature doesn't directly "convince" other browser teams to implement itself. The process, instead, is more like:
1. Browser A adds new non-standard feature.
2. Users like it enough to start using it widely in their apps.
3. Other browsers are now motivated to implement the feature so that those apps work in their browser too.
4. Because of that, there is now incentive to standardize. Finally, the feature becomes a standard.
The sketchy part is that step 2 only works when users deliberately choose to build apps that only work in a single browser. That idea anathema to standards folks, but as far as I can tell, the consensus process does rely on it most of the time. That's how we got JavaScript, XHR, <canvas>, etc.
It's very hard to convince several independent implementation teams that a feature is a good idea if no one is using it yet.