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 22990 - [Custom]: Custom Elements interface should implement the Element interface, not necessarily inherit from it
Summary: [Custom]: Custom Elements interface should implement the Element interface, n...
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: 14968
  Show dependency tree / graph
 
Reported: 2013-08-17 00:59 UTC by Dominic Cooney
Modified: 2013-08-26 18:19 UTC (History)
0 users

See Also:

Attachments

Description Dominic Cooney 2013-08-17 00:59:19 UTC 
"This interface must inherit from the Element interface."

The linked definition of inherit says:

"An interface can be defined to inherit from another interface. If the identifier of the interface is followed by a U+003A COLON (":") character and an identifier, then that identifier identifies the inherited interface. An object that implements an interface that inherits from another also implements that inherited interface."

Thus it seems "inherit" has a specific meaning of one step, not the transitive closure, which seems to be "implements".
Comment 1 Dimitri Glazkov 2013-08-26 18:19:16 UTC 
I see what you're saying. I gave it a stab, but the problem is that "implements an interface" is not defined anywhere. In fact, WebIDL refers to "inherits" as the basic building block. I think we should leave it be for now.