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.

Sign up for GitHub

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

Jump to bottom

Text fields change event called twice #1218

Closed
dholladay opened this issue Aug 2, 2017 · 5 comments
Closed

Text fields change event called twice #1218

dholladay opened this issue Aug 2, 2017 · 5 comments
Labels
invalid The issue is missing information or is not a valid bug/feature request

Comments

@dholladay
Copy link

Steps to reproduce

Use change event on v-text-field

Versions

Vue @latest
Vuetify @v0.14.7
Chrome 60.0.3112.78

What is expected ?

Change event fired once.

What is actually happening ?

Reproduction Link

https://codepen.io/anon/pen/EvgxMj
@johnleider johnleider added the pending review The issue is still pending disposition label Aug 2, 2017
@johnleider
Copy link
Member

Viewing the result like this is deceptive. If you use Vue devtools you can see change is only called once. The other event happens whenever you blur.

@johnleider johnleider added invalid The issue is missing information or is not a valid bug/feature request and removed pending review The issue is still pending disposition labels Aug 2, 2017
@jacekkarczmarczyk
Copy link
Member

@johnleider so you are saying that triggering "change" event on blur is not a bug?

See the codepen https://codepen.io/anon/pen/vJyBdP - IMHO "change" should be triggered only when the value has changed as it is done in native inputs

@johnleider
Copy link
Member

Thank you for a better reproduction.

@johnleider johnleider reopened this Aug 4, 2017
@jacekkarczmarczyk
Copy link
Member

jacekkarczmarczyk commented Aug 4, 2017 •
edited

PR #1251

@juan-tonina juan-tonina mentioned this issue Aug 8, 2017
Closed
@lock
Copy link

lock bot commented Apr 15, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord

@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
invalid The issue is missing information or is not a valid bug/feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dholladay @johnleider @jacekkarczmarczyk