[Bug 21958] [Custom]: Should element registration be associated with a browsing context, not document?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21958

Dominic Cooney <dominicc@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |w3c@adambarth.com

--- Comment #10 from Dominic Cooney <dominicc@chromium.org> ---
I discussed this with abarth. Briefly, having documents without browsing
contexts (like document.implementation.createHTMLDocument('')) use custom
elements seems fraught; would this mean other contextless documents like
XMLHTTPResponse.responseXML or DOMParser-created documents run script where
they couldn't before?

If the idea is to share definitions/prototypes between documents, the spec
really needs something like a unit of related documents.

Another problem with the spec as written--you presumably need to discard the
definitions associated with a browsing context when the document changes, but
there's no language like that in the spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 7 June 2013 08:47:15 UTC