22521 2013-06-30 04:54:56 +0000 [Custom]: Element constructor algorithm bleeds definitions across registration contexts 2013-07-09 20:38:11 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED FIXED P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 90032 0 dominicc 2013-06-30 04:54:56 +0000 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. 90519 1 dglazkov 2013-07-09 20:38:11 +0000 https://dvcs.w3.org/hg/webcomponents/rev/723367db9fa7