@rniwa, good catch ... looks like this issue can be demonstrated in Chrome’s implementation currently like this:
```js
x = document.createElement('x-');
customElements.define('x-', class extends HTMLElement {
constructor() {
super().attachInternals();
}
});
x.attachInternals(); // works
customElements.upgrade(x); // throws
```
--
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/871#issuecomment-675863258