[Bug 22466] [Custom]: Certain documents should not share registration contexts

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

Dominic Cooney <dominicc@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dominicc@chromium.org

--- Comment #1 from Dominic Cooney <dominicc@chromium.org> ---
I think you should investigate a whitelist, not a blacklist.

Straw man: The only thing on the whitelist should be HTML Imported documents.

(From bug 21958)
>> Here's a strawman: document.the_funk() This opts the document into Custom
>> Element processing of the calling document environment.
>> 
>> Not having the_funk is evident everywhere by the spec's use of CONTEXT.
>> These no-active documents do not have a browsing context.
>
> Can you explain this a bit more on that bug? I don't think I understood this
> well.

First, the CONTEXT part. In many algorithms the spec refers to a document's
context. Many documents you're interested in making light up, like template
contents, or DOMImplementation.createDocument, do not have contexts. So that
just needs to be fixed.

How will you fix it? You're going to need to define some mapping from document
to context.

You could ask the running script environment for its context. That has two
problems:

1. It probably does nothing for parsing, and you need the context during
parsing.

2. A given document can be accessed in different contexts, eg a script reaches
into an iframe. For predictable behavior, the mapping should be stable.

So the_funk is a strawman that says there's a method to establish this
association explicitly.

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

Received on Wednesday, 26 June 2013 01:50:01 UTC