[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 #18 from Dimitri Glazkov <dglazkov@chromium.org> ---
Just to enumerate our choices, while the discussion is still in progress:

1) Keep the registry on the document. This ensures there aren't any new
opportunities to run JS, but means we need to special-case the <template> and
the <link rel=import>, which is magic.

2) Move the registry to Window (or "document environment"). Most aligned from
the layering perspective, but scary from security perspective.

3) Build some mechanism/API to share registries between documents and provide
sensible defaults. A bit of work and complexity (not sure on cost/benefit
ratio), but potentially heals both layering and security worries.

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

Received on Wednesday, 19 June 2013 17:37:19 UTC