Some Chrome apps tags (<appview>, <extensionoptions>, <extensionview>,
<webview> etc.) uses Custom Elements V0 as its implementation infra,
but as V0 code will go away, we should migrate to Custom Elements
V1 infra.
Labels: OS-Chrome OS-Linux OS-Mac OS-Windows Status: Started (was: Assigned)
When I tried creating a trivial element via window.customElements.define, I got the following error:
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': "webview" is not a valid custom element name
It looks like we'll need something similar to the v0 RegisterElement where if we call it via a custom binding, then it can use whitelisted internal names.
Comment 1 by kochi@chromium.org
, Jul 26