-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Unrelated data affects style display binding with v-show #10074
Comments
yyx990803
pushed a commit
that referenced
this issue
Jan 11, 2024
yyx990803
added a commit
that referenced
this issue
Jan 11, 2024
edison1105
pushed a commit
to edison1105/vuejs-core
that referenced
this issue
Jan 11, 2024
edison1105
pushed a commit
to edison1105/vuejs-core
that referenced
this issue
Jan 11, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vue version
3.4.8
Link to minimal reproduction
https://play.vuejs.org/#eNqNUr1u2zAQfhVCi1ogEod0KATFSFtkaIe2aDtqocSzzYQiCfIk2zD87j1RkiO7TZBJ1H1Hfj93x+STc3nfQVIkZWi8csgCYOdWlVGtsx7ZkXlYsxNbe9uylFrTylSmsSYg61VQtQZ2N/S8Wwsd4P2MNVZbPyGpB5k+I1tonmq7v7pW8lEAUdMPQuu0QKA/xkqpeqbkXZUI56ok1qZqn4Wt3REyaakSVgQ8aKDScexjTKpAjx0KliqjlYGs1rZ5Sm9mPGotxs9UPBHNsrnkxDYT157x+axFDXo1J1Eq4zpkeHCDgNkpieqz1krQF0L5quTj9Rff7YyHIQZJUYkGVQ9MChSUoTAbCG/hWxQvCWdLJV+Endwk4+CzVrj8MVhDqxGDrCYgVEnBpmjJTUdOCjpsEV0oOG+koWtErXqfG0BuXMvvqY37zqBqIZO2vb/NP+QfiT/gspxDaLPa210AT49UyTSMSMOp2IPPPBgJHvxbaa+uLamvoH/oB/ZTZU4UCgZa3rXaXEXS2NYpDf6HQ0XLfRGN0NruvsUa+g7OXuJA/lN/DDSjwdNPD1HZwj8KvwEc4Yff32FP5zNIk+6GhXoF/AXB6m7QOLZ97owk2Yu+qPZrnLAymz/hYY9gwmxqEBrTiP1xHl9esf4s9za/Pad4+gsOSHxU
Steps to reproduce
What is expected?
After clicking on the "unrelated reactive data change" checkbox, the inline-block div should not be displayed. The style should not be affected by unrelated reactive data, maintaining consistent behavior.
What is actually happening?
After clicking on the "unrelated reactive data change" checkbox, the inline-block div is displayed.
System Info
Any additional comments?
Related issue: #4768
The text was updated successfully, but these errors were encountered: