W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

[Bug 27977] New: [Custom]: mixin pattern: custom elements should be able to extend any base tag with is=

From: <bugzilla@jessica.w3.org>
Date: Sat, 07 Feb 2015 19:02:20 +0000
To: public-webapps@w3.org
Message-ID: <bug-27977-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27977

            Bug ID: 27977
           Summary: [Custom]: mixin pattern: custom elements should be
                    able to extend any base tag with is=
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: rjharmon0316+w3@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14968

As a creator of web components, I'd like to be able to have a component perform
element-type-agnostic concerns, such that it could be mixed in to any specific
tag, thus specializing the prototype for that tag instance.  

This would affect the attachedCallback, where the component author would need
to be given a tag-instance prototype, ideally already prepared for doing mixins
on, and might indicate some fine-tuning of element registration, to support the
late assignment of prototype to tag instance.  I imagine non-mixin custom tags
would have a largely unchanged lifecycle, not least for API compatibility.

Ideally, multiple is= values would allow multiple mixins, each overlaying the
prototype chain defined by the attachedCallback from the prior mixin.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 7 February 2015 19:02:22 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC