Skip to content
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

compat: v-model modifiers do not work on components #12652

Open
markrian opened this issue Jan 6, 2025 · 1 comment · May be fixed by #12654
Open

compat: v-model modifiers do not work on components #12652

markrian opened this issue Jan 6, 2025 · 1 comment · May be fixed by #12654
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: v2 compat

Comments

@markrian
Copy link

markrian commented Jan 6, 2025

Vue version

3.5.13

Link to minimal reproduction

https://codepen.io/markrian/pen/mybremp

Steps to reproduce

Enter numbers into the inputs. The displayed bound values should be numbers, not strings.

For instance:

Expected Actual
Screenshot from 2025-01-06 15-35-10 Screenshot from 2025-01-06 15-34-58

What is expected?

v-model modifiers should work when used on components under @vue/compat.

What is actually happening?

v-model modifiers do not work when used on components under @vue/compat.

System Info

No response

Any additional comments?

You can see the behaviour working as expected under Vue 2 and Vue 3 (proper).

It seems this behaviour was fixed on Vue 3 proper in #2348. Perhaps similar treatment needs to be done for __COMPAT__ code paths?

markrian added a commit to markrian/vuejs-core that referenced this issue Jan 6, 2025
@markrian
Copy link
Author

markrian commented Jan 6, 2025

I have attempted a fix with #12654.

@edison1105 edison1105 added 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: v2 compat labels Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: v2 compat
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants