-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Scope Elements #2957
Comments
not saying this isn't valid, however if you need to do this now there are ways:
The gotcha with these methods is that stencil doesn't replace tag names within a components' internal jsx. For that you can do something like:
|
Hey there, thank you for the patience getting back to you! This idea is interesting for sure. If there are alternatives, please share the. If you want to see something like this in the Stencil code please 👍 ! |
Wanted to bump this. Since October 2023 the first browser tests are getting green: https://wpt.fyi/results/custom-elements/scoped-registry?label=experimental&label=master&aligned |
Hi @splitinfinities |
@raveenita yes, we would love any contributions to this. I am happy to support when any technical question arise. Mind providing some insights in how you would like to implement this? |
Stencil version:
I'm submitting a:
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://stencil-worldwide.herokuapp.com/ or https://forum.ionicframework.com/
Current behavior:
Currently custom elements can conflict when multiple WebComponents have custom elements with the same name on the page.
Expected behavior:
Steps to reproduce:
hello-world-component
that renders "Hello World"hello-world-component
that renders "Hello World 2"Other information:
The text was updated successfully, but these errors were encountered: