5 ms·
Yeah? And what "custom extensions" does Chrome push? NaCl is almost dead, to be replaced by the standard WebAssembly. Everything else is a standard ES2015 spec
by ubertaco 11y ago
Yeah? And what "custom extensions" does Chrome push? NaCl is almost dead, to be replaced by the standard WebAssembly. Everything else is a standard ES2015 spec that Chrome, Edge, and Firefox have implemented (to varying degrees) and Safari has thus far failed to implement.
- pcwalton 11y agoDart? They pushed that one reasonably hard until the writing was on the wall.
- bla2 11y agoWas dart ever part of chrome? I didn't follow that closely, seemed like a separate effort from Google.
- quandrum 11y agoDart never shipped to mainline chrome. Developers could download a special version of chrome with Dart.
- pcwalton 11y agoAdditionally, there was the aborted upstream WebKit effort to allow abstraction over multiple languages with the goal of supporting Dart, and the Oilpan effort had Dart support as a major motivation.
- callahad 11y agoChrome pretty significantly jumped the gun on shipping Shadow DOM and other Custom Element features unprefixed and on by default two years ago while there were significant outstanding objections from other vendors and no stable spec. We're only just now digging out from that mess.
- deleted 11y ago[deleted]
- ubertaco 11y agoThe only objections I remember hearing were from Apple. And implementing something that is in the standardization process with the TC39 still doesn't strike me as "custom extensions".
- mchahn 11y ago> Chrome pretty significantly jumped the gun on shipping Shadow DOM The Atom editor uses shadow dom because Atom is chrome-only. I don't know what is going to happen now that it is deprecated. I see warnings to not use it in the dev console every time I start Atom.
- kuschku 11y agoTheir custom behaviour in the JS apis for HtmlMediaElement come to mind. Half of which plain don’t work, and the other half work on mobile only in onClick handlers.