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

[Bug Report][3.6.15] VNumberInput - when typing using keyboard @update:model-value is not triggerred, counter not visible when clicking #20337

Closed
jakubmatisak opened this issue Aug 15, 2024 · 2 comments · May be fixed by jonathanestefani/crud_vuetify#2, jonathanestefani/crud_vuetify#5 or aurelienfvre/sae401#1
Assignees
Labels
C: VNumberInput T: enhancement Functionality that enhances existing features
Milestone

Comments

@jakubmatisak
Copy link

jakubmatisak commented Aug 15, 2024

Environment

Vuetify Version: 3.6.15
Vue Version: 3.4.38
Browsers: Chrome 127.0.0.0
OS: Windows 10

Steps to reproduce

  1. write numbers to VNumberInput using keyboard, not using buttons.
  2. expecting to see validator counting or rules updating immediately
    (@update:model-value is not triggered)

I have also found that counter is not visible when clicking on buttons up/down - I canot say if this is intended behaviour but I would expect to see it there - to have app consisent - it is there in other types of input.

Thanks.

Expected Behavior

  1. trigger update model instantly as in VTextField - because counter is not counting and rules validator not working immediately.

Actual Behavior

  1. update model is triggerd after leaving field and it is clicked outside VNumberInput

Reproduction Link

[https://play.vuetifyjs.com/#...](https://play.vuetifyjs.com/#eNpdj8tuwyAQRX9lxCatVIduuonsqP2AbrupuyD2RLUEA+LhjcW/Z4AkirKxPGcucO7vJoKf5Jdz+zWhOIg+onFaRTyOBNCvnXKu/tZhshTVQuiviGFwio6wbUDm5CFn6GVF98DaUTIn9N1CLkX4TG7m6w/Gzqi7VemEwyj+Fc0avwv7KWgUMNlEET0vP3iSNwn5bFFIk+zlgzyPYfKLixAwptZhMc76CBt4PEOGs7cGdtx7V+LAL1KIrcdQIi/vr4+LZ0cOVX0YuH+zK2f3V9iWheei1mRYQ+Q3SlrXz98FGl2BZA==)

@yuwu9145
Copy link
Member

This behaviour is intentional: #20171

@yuwu9145 yuwu9145 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2024
@KaelWD
Copy link
Member

KaelWD commented Aug 15, 2024

Perhaps a middle ground would be good? if (isValidNumber && clampToRange(value) === value) emit()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment