This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23018 - [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases
Summary: [Custom]: Consider creating registries for HTML documents created through DOM...
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-20 01:43 UTC by Dominic Cooney
Modified: 2015-07-06 08:18 UTC (History)
0 users

See Also:

Attachments

Description Dominic Cooney 2013-08-20 01:43:15 UTC 
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.
Comment 1 Dominic Cooney 2013-08-20 01:53:56 UTC 
Oops, instead of

doc3 = document.implementation.createHTMLDocument()

Of course I meant

doc3 = doc2.implementation.createHTMLDocument()
Comment 2 Hayato Ito 2015-07-06 08:18:39 UTC 
Moved to https://github.com/w3c/webcomponents/issues/236