Custom Element V0 via HTMLTemplate
Reported by
andrea.g...@gmail.com,
Oct 27 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Steps to reproduce the problem: 1. create a template 2. inject as HTML a registered Custom Element V0 3. see element never getting upgraded even once appended to a live node What is the expected behavior? Custom Elements V1 created inside a template triggers constructor and connected once appended live through the template.content. This does not happen with Custom Elements V0. What went wrong? There are popular projects such A-Frame still using only Custom Elements V0 API and if their elements are created through templates their elements won't ever work. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 62.0.3202.62 Channel: n/a OS Version: Flash Version: Chrome is the only one shipping V0. If you are not planning to fix this issue, please drop this API 'cause polyfills for V0 work better than native implementation and V1 down-filled as V0 would work better too. Thank you
,
Nov 1 2017
Thanks for reporting the issue. @andrea.giammarchi-- Could you please provide the sample test file including the complete code in html/jsfiddle or help us in executing the attached js file. Thanks!
,
Nov 1 2017
,
Nov 1 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 2 2017
Able to reproduce this issue on reported version 62.0.3202.62, latest stable 62.0.3202.75 and on latest canary 64.0.3255.3 using Windows 10 and Ubuntu 14.04 and Mac 10.12.6 Manual Bisect Info: ================ Good build: 54.0.2811.0 Bad build: 54.0.2812.0 You are probably looking for a change made after 408581 (known good), but no later than 408586 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/77fc296fc1692c95757eb5bba1ddd8c3c45061d7..92d6c18fcb5614c9d3abc85ce54c1c619b42f535 Suspecting same from changelog. Review-URL: https://codereview.chromium.org/2184223004 Unable to assign to @sigbjornf, hence assigning to Ojan as one of the reviewer @sigbjornf: Please confirm the bug and help in re-assigning if it is not related to your change
,
Nov 4 2017
,
Nov 6 2017
,
Nov 7 2017
Lower to Pri-3 since we don't have enough resources to work this.
,
Nov 7
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 8
We won't fix Custom Elements V0 issues. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by kochi@chromium.org
, Oct 30 2017