[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 #11 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #10)
> 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?

This we can mitigate easily. There's a
http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#scripting-flag,
and it's explicitly set for documents, created that way. We should explicitly
check for that flag.

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

I wonder if "browsing context" is simply the wrong abstraction to associate
with. Perhaps
http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#document-environment
is the right one.

> 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.

Associating with document environment should fix that?

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

Received on Tuesday, 18 June 2013 17:34:14 UTC