[Bug 22521] New: [Custom]: Element constructor algorithm bleeds definitions across registration contexts

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

            Bug ID: 22521
           Summary: [Custom]: Element constructor algorithm bleeds
                    definitions across registration contexts
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dominicc@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

Step 3.7 of the element constructor algorithm may bleed a definition across
registration contexts. For example:

1. Create a Custom Element in an iframe.
2. Disclose the constructor to a different window using JavaScript.
3. Call the constructor from JavaScript in that window.

Step 3.7 is problematic because it initializes the element and calls the ready
callback. But this could be happening in a different registration context (and
in fact the original frame may be gone.)

I think the element constructor algorithm needs to add a step:

3.0 If DOCUMENT's CONTEXT is different to the CONTEXT associated with
DEFINITION, throw an InvalidStateError.

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

Received on Sunday, 30 June 2013 04:54:58 UTC