5 ms·
Seeing a bad trend here lately, and at IO, where they continually talk about Chrome as a platform. Not the web, Chrome. I read Chromium bugs about Chrome specif
by MatthewPhillips 13y ago
Seeing a bad trend here lately, and at IO, where they continually talk about Chrome as a platform. Not the web, Chrome. I read Chromium bugs about Chrome specific APIs and never see any indication that there is intent at standardization. To be clear, I believe in browser vendors innovating with their own APIs with an eye towards eventually standardization. This is what Mozilla is doing through WebAPI, for example, but I don't hear anything like that from the Chrome team. What I see is that parts of Google are involved in web standards, of course, but particularly Chrome seems entirely focused on themselves as the platform.
- eurleif 13y agoWell, this API has been submitted to WHATWG: http://wiki.whatwg.org/wiki/RequestAutocomplete http://wiki.whatwg.org/wiki/RequestAutocomplete
- pixelcort 13y agoA quick test would be this: are there any APIs in Stable/Release versions of Chrome that have not been submitted to any standards group?
- bzbarsky 13y agoSure there are (some inherited from WebKit). Though note that submitting and then completely ignoring the standards group (which has also happened) is not much better than not submitting at all. Especially if the submission doesn't actually give much more than the name of the API and a general idea of what it does.
- YesThatTom2 13y ago"completely ignoring the standards group"? Look at their off-line standard. They took it to the standardization body who changed it so completely that it was a different beast. Google did the right thing and phased out their old legacy stuff and switched to the standard. In fact IIRC they didn't even put the legacy stuff in Chrome.
- bzbarsky 13y agoSure. There are lots of parts of Google and Chrome that play very nice with standards groups and whatnot. And there are various other parts that don't.