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 28158 - [Custom]: inflexible extends as fixed element type
Summary: [Custom]: inflexible extends as fixed element type
Status: RESOLVED MOVED
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 treegraph
 
Reported: 2015-03-07 00:10 UTC by Dimitri Glazkov
Modified: 2015-07-06 08:09 UTC (History)
2 users (show)

See Also:


Attachments

Description Dimitri Glazkov 2015-03-07 00:10:02 UTC
From: https://github.com/w3c/webcomponents/issues/33

rjharmon commented on Jan 25

I'd like to be able to specify any type (or perhaps certain types) of tags, with is= to augment functionality of any element. The initialization sequence I'm imagining is passed the native element instance, and then the component would be able to add its own capabilities to that instance's prototype chain (could also choose to prepare the prototype chain so that element.prototype is already distinguished from that element's native prototype, as a helpful refinement to developers).

A similar technique could be used to add multiple mixins to a tag, assuming they'd been designed them to be complementary/concerned with orthogonal aspects of the markup/content. I think of that as with= rather than is=.
Comment 1 Hayato Ito 2015-07-06 08:09:36 UTC
Moved to https://github.com/w3c/webcomponents/issues/143