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 21811 - [Custom]: Making HTMLElement the element interface of unresolved elements needs clarification
Summary: [Custom]: Making HTMLElement the element interface of unresolved elements nee...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 18720
  Show dependency tree / graph
 
Reported: 2013-04-24 13:12 UTC by Dominic Cooney
Modified: 2013-04-24 20:52 UTC (History)
0 users

See Also:

Attachments

Description Dominic Cooney 2013-04-24 13:12:57 UTC 
The spec says: "When an unresolved element is created, its element interface must be: the HTMLElement, if the namespace is HTML Namespace;"

I think it would be appropriate to add commentary about the implications of this for implementers, because the HTML spec says:

"The HTMLUnknownElement interface must be used for HTML elements that are not defined by this specification (or other applicable specifications)."

Assuming a user agent treats Custom Elements as an applicable specification, this means any element whose name is valid will now have HTMLElement and not HTMLUnknownElement as an interface.
Comment 1 Dimitri Glazkov 2013-04-24 20:52:00 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/bd93a00feb0a