- From: <bugzilla@jessica.w3.org>
- Date: Sat, 07 Mar 2015 00:10:02 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28158
Bug ID: 28158
Summary: [Custom]: inflexible extends as fixed element type
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: dglazkov@chromium.org
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
Blocks: 14968
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=.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 7 March 2015 00:10:08 UTC