New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 726628 link

Starred by 1 user
Status: Duplicate
Merged: issue 660759
Owner:
█ dominicc@chromium.org
Last visit > 30 days ago
Closed: May 2017
Cc:
domenic@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Deprecate Custom Elements v0

Reported by seandenn...@gmail.com, May 26 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3107.4 Safari/537.36

Steps to reproduce the problem:
[Feature Request]

What is the expected behavior?

What went wrong?
Seeing as Blink was the only engine to implement v0 and v1 is already out, it is time to push to a full v1 support

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 60.0.3107.4  Channel: dev
OS Version: 10.0
Flash Version:

Comment 1 by dominicc@chromium.org, May 30 2017

Components: -Blink>WebComponents Blink>HTML>CustomElements
Labels: OS-Android OS-Chrome OS-Linux OS-Mac
Mergedinto: 660759
Owner: dominicc@chromium.org
Status: Duplicate (was: Unconfirmed)
We're working on it.

document.registerElement is used a lot so I doubt we can remove it yet without breaking too many sites. The plan is to enable customized built-in elements ( Issue 648828 ) so there's a way forward for most users, and then deprecate and remove document.registerElement.

HTH, feel free to star that bug for updates, send me any questions, etc.
►

Sign in to add a comment