Skip to content

[Bug Report][3.8.0] VNumberInput append-inner max button don' update value #21213

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

Open
jfrag opened this issue Apr 4, 2025 · 4 comments · May be fixed by #21217
Open

[Bug Report][3.8.0] VNumberInput append-inner max button don' update value #21213

jfrag opened this issue Apr 4, 2025 · 4 comments · May be fixed by #21217
Assignees
Labels
C: VNumberInput has workaround T: bug Functionality that does not work as intended/expected

Comments

@jfrag
Copy link

jfrag commented Apr 4, 2025

Environment

Vuetify Version: 3.8.0
Vue Version: 3.5.13
Browsers: Chrome 135.0.0.0
OS: Linux x86_64

Steps to reproduce

Click on max btn doesn't change the value

Expected Behavior

change value to max

Actual Behavior

doesn't change the value

Reproduction Link

https://play.vuetifyjs.com/#...

@jcjp jcjp added T: bug Functionality that does not work as intended/expected C: VNumberInput labels Apr 4, 2025
@jcjp jcjp self-assigned this Apr 4, 2025
@github-actions github-actions bot removed the S: triage label Apr 4, 2025
@jcjp
Copy link
Contributor

jcjp commented Apr 5, 2025

On you reproduction link, I tested it and it works if it does not have the increment and decrement buttons. It actually sets the value to max on both fields.

@J-Sek
Copy link
Contributor

J-Sek commented Apr 5, 2025

I guess it might have something to do with precision behavior - hiding trailing zeros on focus. I wish it could be as simple as @click.stop=... to prevent focus on the inner button click, but it does not really help. The only workaround I see is to change #append-inner into #append and move that button inside with CSS transform: translateX(...).

Internally I am considering some change in line 107 as it is exactly what prevents the input from accepting "external" change upon the click.

@J-Sek
Copy link
Contributor

J-Sek commented Apr 5, 2025

Even easier workaround: @click@mousedown (and probably @keydown.space and @keydown.enter to keep it accessible)

@jcjp
Copy link
Contributor

jcjp commented Apr 5, 2025

Even easier workaround: @click@mousedown (and probably @keydown.space and @keydown.enter to keep it accessible)

Feel free to work and fix on this, I am still actually investigating and it seems you already have some solutions on your mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: VNumberInput has workaround T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants