-
-
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
Custom Web Elements/Components receive null
instead of false
on subsequent re-render
#10324
Comments
duplicated of #9006 |
I'm not sure about that, on the surface it seems to be a different use-case since I don't use the default value, I can even make my prop to be required. However, it is related, so I imagine that the same fix could resolve both issues at the same time. |
wangdaoo
pushed a commit
to wangdaoo/core
that referenced
this issue
May 30, 2024
…js#9012) Partially fixes vuejs#9006 Fixes vuejs#10324
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vue version
3.4.18
Link to minimal reproduction
https://jsfiddle.net/uwegz5y8/23/
Steps to reproduce
Boo: false; typeof: boolean
- as expected, becauseboo
attribute is not setBoo: true; typeof: boolean
- as expected, because nowboo
attribute is setBoo: null; typeof: object
- unexpected, sinceboo
attribute is removed - we expect to receivefalse
just like in the 2nd step previouslyWhat is expected?
false
What is actually happening?
null
System Info
No response
Any additional comments?
Kinda related: #9697
The text was updated successfully, but these errors were encountered: