Re: [w3c/webcomponents] defining and instantiating customized built‐in elements as if they were autonomous custom elements (#613)

I feel like https://github.com/w3c/webcomponents/issues/509#issuecomment-264720715 is easier to understand, and in that case your example following that pattern would be:

```js
let plasticButton = document.createElement("plastic-button");
console.log(plasticButton.localName);          // will output "plastic-button"
console.log(plasticButton.getAttribute("is")); // will output "button"
```

It would be great if this pattern would hold for all of customized built-in elements (custom classes that extend from built-in classes), built-in elements, and autonomous custom elements (custom classes that don't extend from built-in classes).

It would also be super if `is=""` (or `extends=""`) would accept customized built-in element names or autonomous custom element names, not just built-in element names.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/613#issuecomment-264722545