5 ms·
Just to set the record straight on the part I'm familiar with, "Custom Elements V0" was never a web standard. It was a proposal, which Chrome implemented and s
by bzbarsky 7y ago
Just to set the record straight on the part I'm familiar with, "Custom Elements V0" was never a web standard. It was a proposal, which Chrome implemented and shipped without getting everyone else on board, and which turned out to have significant enough problems that a somewhat different thing got standardized and shipped in all browsers ("Custom Elements V1").
- dmitriid 7y agoOnce something is shipped, people will rely on it. For example, quite famously, Youtube did for a very long time (until this year IIRC). AMP used to use it. There are several polyfills available. Several Polymer versions targeted v0. Etc. etc. It's not specifically Google's fault that they are removing support for these, but, once again, that's the state of the world: browsers are lrage complex platforms that may and will break your app.
- bzbarsky 7y agoSure. Unshipping things is always hard, and likely to break people. But there's still a difference between unshipping support for a standard and unshipping support for a non-standard technology that only you ever implemented. In the latter case, people should be a lot more wary of depending on the technology in the first place. While it's true that browser updates may break your app, it's also true that there are ways to write the app so as to minimize the risk of such breakage. Using Custom Elements V0 was _not_ a good way to avoid potential breakage...