As of today, things still not working:

  1. `new CustomBuiltIn()` throws `Illegal constructor`
  2. `document.createElement("button", { is: "plastic-button" })` as specified in the official example ( https://html.spec.whatwg.org/multipage/scripting.html#custom-elements-customized-builtin-example ) creates `<button is="[object Object]"></button>`
  3. `document.createElement('button', 'plastic-button')` would create a proper `<button is="plastic-button"></button>` but it won't even bother using the defined constructor

yurak is working on this.

The assigned owner "yurak@google.com" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Is this still being worked on? Can I somehow help this?

Yes, it is still being worked on--yurak's internship has finished.

mr.avgp, we'd love help, could you send me email and describe a little about your skills and interests and I'll help.

Hi. Any updates on this?

meanwhile I have some failing tests and try to implement the fixes, but I
am a little swamped with work right now =(

Just FYI: Baby steps in the right direction. ;-)

Deleted: fuck_yes_it_works.png 108 KB

	fuck_yes_it_works.png 108 KB View Download

How is this going? The community is keen to try this out! Thanks for keeping going on this.

You can try this today for DIV and P by setting the --enable-blink-features=CustomElementsBuiltin flag. Feedback welcome.

In Canary with this flag enabled I get 2 kinds of errors.

1. Chrome tells me it's an unsupported flag (even though there is a difference with a without it)

2. Illegal constructor, same I get when I <big-button> the element instead of <button is="big-button">

No error 2 without the [is].

No error 1 without the flag, but also no other errors or messages, probably because it doesn't do anything.

The real test for me is to make custom TD elements that work without webcomponents (so <td is="custom-td">, not <custom-td>), but I don't have that test handy.

Deleted: screen-chrome-canary-customelements-errors.png 137 KB

	screen-chrome-canary-customelements-errors.png 137 KB View Download

Since BUTTON is not DIV or P, that might be my fault =) Sorry!

`<p is="big-p">Huge paragraph!</p>` works (messages and custom shadow root), but

`<big-p>Huge paragraph!</big-p>` doesn't work: no messages, no errors, <big-p> just falls back to a non-existing element

This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge

Bulk edit bugs owned by dominicc@

We don't need a launch-tracking bug for this feature.
Please use  Issue 648828  if you have any comments on this feature.