28441 2015-04-08 15:49:50 +0000 [Shadow]: Declarative Shadow DOM 2015-05-27 02:50:28 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED P2 normal --- 15480 1 dglazkov dglazkov eoconnor hayato mike mjs public-webapps rniwa timdream public-webapps-bugzilla oldest_to_newest 119369 0 dglazkov 2015-04-08 15:49:50 +0000 From: https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0052.html "Mostly for performance it would be nice if the composed tree could be serialized and cached. That way first render only requires HTML and CSS with JavaScript kicking in at the end. We reasoned it might not be too hard to add something like <shadowroot> given our experience with <template>. The only difference would be that <shadowroot> itself would also not be appended to the tree and that the DocumentFragment nee ShadowRoot is associated with "its parent"." 119382 1 dglazkov 2015-04-08 16:21:10 +0000 Here's a fairly simple implementation of this using custom elements and templates: http://jsbin.com/xuheb/4/edit I think this is a great example of: a) using type extensions to avoid more hard-coded parsing behaviors b) extensible web in action -- no need to wait on spec/browsers to ship this c) custom element upgrades being helpful in avoiding additional tree traversals and deferring running of the script until whenever you actually need the tree. 120498 2 hayato 2015-05-27 02:50:28 +0000 Moved to https://github.com/w3c/webcomponents/issues/71