23018 2013-08-20 01:43:15 +0000 [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases 2015-07-06 08:18:39 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED MOVED P2 normal --- 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 92314 0 dominicc 2013-08-20 01:43:15 +0000 As written, if you have an document with a registry, then do doc2 = document.implementation.createDocument(...) to create a non-HTML, etc. document (ie one that does not get associated with a registry) and then turn around and do doc3 = document.implementation.createHTMLDocument() the speced behavior is for doc3 to not have a document/not process Custom Elements. A possible alternative semantics is for doc3 to get a new, separate registry from the original document. The nice property this gives you is all documents that *could* process Custom Elements (ie right kind of document) *do* process Custom Elements, and just which registry they're associated with differs. 92315 1 dominicc 2013-08-20 01:53:56 +0000 Oops, instead of doc3 = document.implementation.createHTMLDocument() Of course I meant doc3 = doc2.implementation.createHTMLDocument() 121764 2 hayato 2015-07-06 08:18:39 +0000 Moved to https://github.com/w3c/webcomponents/issues/236