3 ms·
http://jonrimmer.github.io/are-we-componentized-yet/ http://jonrimmer.github.io/are-we-componentized-yet/ https://platform-status.mozilla.org/#html-imports http
by 101km 9y ago
http://jonrimmer.github.io/are-we-componentized-yet/ http://jonrimmer.github.io/are-we-componentized-yet/
https://platform-status.mozilla.org/#html-imports https://platform-status.mozilla.org/#html-imports
HTML Imports are only implemented in Chrome and it is going to stay that way, Firefox and Safari aren't having it.
This is arguably a bummer but not critical for Web Components.
What is critical is that Custom Elements and Shadow DOM (V1) are in the latest Chrome and Safari but not on the horizon for Firefox and Edge. Supposedly it is planned, but unclear when it will actually arrive. 2018?
- ergo14 9y agoAccording to announcements made by google guys on few conferences both IE and Firefox actively work on implementations.
- greenyouse 9y agoThe Browser Support chart on webcomponents.org shows that they're working on it[1]. I think it's a pretty good way to track web component compatibility (outside of caniuse). [1]https://www.webcomponents.org/ https://www.webcomponents.org/
- H1Supreme 9y agoI was watching the Google I/O feed and one of the Polymer guys was like, "Web Components are here, everything's great!". But, that's obviously not the case. Unless I missed something in the 2.0 for Polymer, they still use html imports. Which, will need polyfilled on everything but chrome. I've been rooting for web components for a long time now. But, I still don't think it's ready for prime time. Vue has been serving me well, and feels just like web components when writing code.