-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Since vue 3.4.15 named slots not render with component same name like html tags #10395
Labels
Comments
nestle49
changed the title
Since vue 3.4.15 slots not render with component same name like html tags
Since vue 3.4.15 named slots not render with component same name like html tags
Feb 24, 2024
It was introduced in 3.4.0, handling core/packages/compiler-core/src/tokenizer.ts Lines 553 to 562 in bfe6b45
|
OnlyWick
pushed a commit
to OnlyWick/core
that referenced
this issue
Feb 27, 2024
wangdaoo
pushed a commit
to wangdaoo/core
that referenced
this issue
May 30, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vue version
3.4.19
Link to minimal reproduction
https://github.com/nestle49/minimalReproduction
Steps to reproduce
What is expected?
Names slots are visible or warn
What is actually happening?
Named slots don't render
System Info
Any additional comments?
We used named slots and the name of the TextArea.vue component was the same as the textarea html tag. Before version 3.4.15 this worked, after updating to version 3.4.15 the named slots stopped rendering, and we did not receive any console warnings or any errors in the logs at all, as if everything was fine
I understand that this is not a very good practice, but the problem is that we learned about this after receiving broken sites. Could you print a warning to the console that components are using a reserved word? In this case, the html tag
Or at least about slots not being rendered, if possible
The text was updated successfully, but these errors were encountered: