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 21817 - [Custom]: Unresolved element interface must take type extensions into account
Summary: [Custom]: Unresolved element interface must take type extensions into account
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:
Whiteboard:
Keywords:
Depends on:
Blocks: 18720
  Show dependency tree / graph
 
Reported: 2013-04-24 18:16 UTC by Dimitri Glazkov
Modified: 2013-04-24 20:52 UTC (History)
0 users

See Also:

Attachments

Description Dimitri Glazkov 2013-04-24 18:16:32 UTC 
"When an unresolved element is created, its element interface must be:

the HTMLElement, if the namespace is HTML Namespace;
the SVGElement, if namespace is SVG Namespace; or"

This is not quite right. I should take type extensions into the account. For <button is="foo-bar">, the element interface must be HTMLButtonElement.
Comment 1 Dimitri Glazkov 2013-04-24 20:52:16 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/bd93a00feb0a