4 ms·
Chrome 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
by callahad 11y ago
Chrome 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.