4 ms·
> They're not doing this as they see fit. Sure they are. It's already part of Chromium. https://cs.chromium.org/chromium/src/content/browser/portal/portal_bro
by rangerpolitic 7y ago
> They're not doing this as they see fit.
Sure they are. It's already part of Chromium.
https://cs.chromium.org/chromium/src/content/browser/portal/portal_browsertest.cc?g=0 https://cs.chromium.org/chromium/src/content/browser/portal/...
It's been there since at least last August.
- cromwellian 7y agoIt's turned off by default.
- throwaway2048 7y agonot for long
- cromwellian 7y agoSure, if it gets approved as a standard. Why not go look at the history of other HTML, CSS, and JS API additions, and the way they were staged, and what percentage shipped without agreement from other stakeholders? Start at https://www.chromestatus.com/features/schedule https://www.chromestatus.com/features/schedule you can drill down from there, for each feature, you can see links to W3C, WICG, TC'39, or whatever repositories, complete with discussion, and status from other browser vendors. Yes, Chrome has shipped proprietary API features "on by default" before without buy-in from everyone else (e.g. NaCL), but so has Mozilla. The question is, are these the exception, or the rule? And in my view, most of the Web's evolution in the past few years has been way more open and participatory than the 90s/00s Netscape/IE era.