W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

[Bug 28544] New: Custom elements should not upgrade elements by setting prototype

From: <bugzilla@jessica.w3.org>
Date: Wed, 22 Apr 2015 23:45:08 +0000
To: public-webapps@w3.org
Message-ID: <bug-28544-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28544

            Bug ID: 28544
           Summary: Custom elements should not upgrade elements by setting
                    prototype
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: rniwa@webkit.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

Discussed here:
https://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0158.html
https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0083.html

We shouldn't support upgrading of existing elements since it leaves the
corresponding DOM objects with a wrong identity.

This is also not a normal programming model. Even with ES6 modules, we don't
create a dummy modules while modules are loading and later automatically
replace them under the foot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 22 April 2015 23:45:09 UTC

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