Yes, I&#x27;m definitely looking forward to the Real Shadow DOM being browser-supported. I was unable to use the full webcomponents polyfill in my own application, as it introduced gamebreakers with contenteditable-based rich text editors [0]. Putting polymer anywhere on my page meant my rich text editor (quilljs fwiw) broke on non-chrome browsers, even through I wasn&#x27;t doing anything polymeresque with the editor. It was just the polyfill interacting poorly with the browser&#x27;s range implementation. In my case (my application also heavily leaned on angular for routing and page-level templating), I couldn&#x27;t mix-and-match angular and polymer and also maintain cross-browser support of the text editor.<p>But I still am _super_ excited about the future of the webcomponents world. I mean, if nothing else, having well-namespaced element ids (if I have two editor components on the page, I can&#x27;t just grab &quot;#dateinput&quot;) will be great. I love the idea of directly attaching properties to DOM nodes, encapsulating templates, and projecting content into viewports. It&#x27;s seriously rad. I am 100% on board with the notion, it&#x27;s just the polyfill in the meantime that&#x27;s problematical.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;webcomponents&#x2F;webcomponentsjs&#x2F;issues&#x2F;212" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;webcomponents&#x2F;webcomponentsjs&#x2F;issues&#x2F;212</a>