[webcomponents] Inheritance in Custom Elements (Was Proposal for Cross Origin Use Case and Declarative Syntax)

On Nov 11, 2013, at 4:12 PM, Dimitri Glazkov <dglazkov@chromium.org> wrote:
> 3) The approach pollutes global name space with constructors. This had been voiced many times as unacceptable by developers.
> 
> 4) How does build a custom element that uses <name-card> as its base element? What about <div> or any other HTML element?
> 
> The last one remains to be the hardest. The tortured inheritance support is what killed <element> in the first place. We can't ignore the inheritance, since it is clearly present, in both DOM and JS. If we attempt to punt on supporting it, our decisions cut off the opportunities to evolve this right in the future, and will likely leave us with boogers like multiple syntaxes for inheritance vs. non-inheritance use cases.

What exactly are you referring to by inheritance support?

Inheritance from all builtin elements (e.g. subclasses of HTMLElement)?

Or inheritance from custom elements authors have defined?

And could you give us a pointer for a list of concrete use cases?

- R. Niwa

Received on Friday, 6 December 2013 03:56:43 UTC