[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

--- Comment #15 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #14)
> (In reply to comment #13)
> > "document environment" definition is a bit too squishy in HTML spec. We
> > should just use the Window object?
> 
> I've lost the use-case we're trying to solve with this change. Is the idea
> to share custom elements among groups of same-origin (related?) documents or
> to make document.implementation.crweateHTMLDocument().register work by
> registering the new custom element somewhere where "document" can get at it?

The latter. I think this statement is right: for one set of built-ins, there's
also one custom element registry. This is important for <template> and later
<link rel="import">.

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

Received on Tuesday, 18 June 2013 22:21:30 UTC