5 ms·
For the moment, it doesn't really have great browser support and less intent to implement than some other features of the OWP. Whereas service workers at least
by dccoolgai 10y ago
For the moment, it doesn't really have great browser support and less intent to implement than some other features of the OWP. Whereas service workers at least had Mozilla pushing along with it, Google seems to be "going it alone" a bit more on Polymer and having a tougher time building a coalition for it.
- nawitus 10y agoHmm, I've found that the polyfills work fine, if you need to target IE11 and latest Firefox/Chrome. Even old Chrome versions work well with the polyfill.
- andreapaiola 10y agoThe shadow DOM works in IE, all the spec?
- nawitus 10y agoThe shadow DOM polyfill works fine in IE. There are a few problems with IE though, the main one I've encountered is that dom-repeat doesn't work inside table.
- andreapaiola 10y agoFirefox? Safari iOs?
- nawitus 10y agoYes to Firefox. I don't test Safari.
- andreapaiola 10y agoFor a public site is important...
- robdodson 10y agoThis is not true. All of the browsers are on board to ship Web Components and have been actively engaged in the standards discussions. Safari just shipped Shadow DOM v1 in Safari Technology Preview. https://webkit.org/blog/6017/introducing-safari-technology-preview/ https://webkit.org/blog/6017/introducing-safari-technology-p... Edge are actively working on Shadow DOM and Custom Elements support https://blogs.windows.com/msedgedev/2015/07/15/microsoft-edge-and-web-components/ https://blogs.windows.com/msedgedev/2015/07/15/microsoft-edg... Firefox is working on Shadow DOM and Custom Element support as well. The odds are good that other browsers will begin landing these features in their stable releases in 2016.