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

Only emit input on actual input events #711

Merged
merged 1 commit into from
Feb 10, 2019
Merged

Conversation

TaylorDale
Copy link
Contributor

@TaylorDale TaylorDale commented Dec 10, 2018

Separated the input event from the change event, which will still occur upon any change of value (programmatic, user, whathaveyou).

The input event now only occurs upon user input as is standard with all other components and form fields.

This resolves #659 #573 #545 #526 #504 #455 #533

Seperated it from the change event, which will still occur upon any change of value (programmatic, user, whathaveyou)
@rurodev
Copy link

rurodev commented Dec 21, 2018

Would need exactly this change to use this component, what are the chances to have it merged? Otherwise I need to look for an alternate.

@shredmaster
Copy link

i also need this feature to use this component. anyone have a workaround?

@TaylorDale
Copy link
Contributor Author

You can just install my fork with Npm to use it right now

@angeliski
Copy link

Hey @sagalbot Any update about that merge? You need some help about that?

@sagalbot sagalbot self-assigned this Feb 10, 2019
@sagalbot sagalbot added this to the v2.6 milestone Feb 10, 2019
@sagalbot sagalbot merged commit 435ae6e into sagalbot:master Feb 10, 2019
@sagalbot
Copy link
Owner

Thanks @TaylorDale, will be in 2.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How to add default value without triggering @input event?
5 participants