- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 Nov 2013 19:59:46 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23839 Bug ID: 23839 Summary: [Custom]: Template document should not share registry with its document Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: dglazkov@chromium.org QA Contact: public-webapps-bugzilla@w3.org CC: dominicc@chromium.org, mrbkap@gmail.com Blocks: 14968 This was brought up by the Polymer team. In their custom elements, they have to special-case custom element being in a template and short-circuit their "created" callbacks to provide impression of "inertness". Also brought up here: http://techblog.ironfroggy.com/2013/11/5-reasons-web-components-arent-ready.html (see missing item 3). This seems like a common pattern, and it's easily rectified by removing the line in spec where we share the registry with the template document. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 15 November 2013 19:59:47 UTC