Hacker News Reader

I don't know about the CSS stuff that spawned this thread, but the rest of the shadow DOM stuff is polyfilled to work in other browsers:

https://github.com/Polymer/ShadowDOM

View on HN

This is speculation: The reason Google is moving forward quickly with Shadow DOM implementation is that this polyfill is dog slow. Think about what it takes to make DOM invisible in the browser in a polyfill- overriding every DOM method to filter out shadowed nodes. I've heard reports of 10x slowdowns on DOM operations with this polyfill in place. The kicker? Web Components (specifically Custom Elements) lose almost all their encapsulation without Shadow DOM. Those of us who are betting heavy on Web Components as The Future™ are pretty anxious about this.

> The reason Google is moving forward quickly with Shadow DOM implementation is that this polyfill is dog slow.

I'm not sure what you mean by "moving forward quickly". They've been hammering on this in the public eye for over three years. How many more years of salary should they pay before they get it out the door? At some point, you just have to ship.

Reply on news.ycombinator.com