Re: [w3c/webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239)

> By the way, if we're allowing exotic non-ASCII characters like emoji, we probably don't need the hyphen requirement in those tag names since the requirement exists for the forward compatibility with future HTML documents, and I don't think we'd ever add an HTML element with an emoji in its tag name.

Why are we so worried about custom element names conflicting with possible future tag names?

I propose that we should be allowed to override any element we wish, and in a per-shadow-root basis (not just on document):

```js
import AwesomeImageElement from `awesome-img`
shadowRoot.registerElement('img`, AwesomeImageElement)
shadowRoot.appendChild(shadowRoot.createElement('img'))
```

If we allow overriding of native elements, then there will be no problem introducing native elements; existing apps will continue to work, having their custom elements in place.

Please see the following threads for more details and examples:

- [[Custom Elements] Not requiring hyphens in names](https://discourse.wicg.io/t/custom-elements-not-requiring-hyphens-in-names/1439)
- [[proposal] Register custom elements onto ShadowDOM roots](https://discourse.wicg.io/t/proposal-register-custom-elements-onto-shadowdom-roots/1440)

---
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/239#issuecomment-210543744