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 22833 - [Custom]: Declarative syntax does not account for out-of-order declarations
Summary: [Custom]: Declarative syntax does not account for out-of-order declarations
Status: RESOLVED LATER
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: 22941
  Show dependency tree / graph
 
Reported: 2013-07-29 21:08 UTC by Dimitri Glazkov
Modified: 2013-10-07 16:30 UTC (History)
0 users

See Also:

Attachments

Description Dimitri Glazkov 2013-07-29 21:08:36 UTC 
In http://parkour.mtv/webcomponents/spec/custom/index.html#dfn-create-custom-element-declaration,

"If BASE is empty, let INTERFACE be HTMLElement
Otherwise, let INTERFACE be the element interface for BASE and HTML Namespace"

Suppose that the BASE is also a custom element, and its declaration hasn't been loaded yet. This will turn this declaration into a dud. That's bad.