This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21129 - Custom element registration behavior with HTMLElement prototype from a different window.
Summary: Custom element registration behavior with HTMLElement prototype from a differ...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL: https://dvcs.w3.org/hg/webcomponents/...
Whiteboard:
Keywords:
Depends on:
Blocks: 18720
  Show dependency tree / graph
 
Reported: 2013-02-26 20:23 UTC by William Chen
Modified: 2013-04-22 23:16 UTC (History)
1 user (show)

See Also:

Attachments

Description William Chen 2013-02-26 20:23:51 UTC 
"Otherwise, if INTERFACE does not inherit from HTMLElement, throw a NamespaceError and stop."

Element registration is per document but inheritance is global, this mismatch in the spec makes it unclear what should happen when a custom element is registered with a prototype that "inherits" from HTMLElement (or SVGElement) using the HTMLElement.prototype from another window.
Comment 1 Dimitri Glazkov 2013-02-26 20:25:56 UTC 
Oh, good point. I should add a document check to make sure registration throws if fed a prototype from a different document.
Comment 2 Dimitri Glazkov 2013-04-22 23:16:33 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/5a6aa311e8e4