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

set target value onchange client-side #694

Merged
merged 2 commits into from
Feb 28, 2022
Merged

set target value onchange client-side #694

merged 2 commits into from
Feb 28, 2022

Conversation

rmorshea
Copy link
Collaborator

@rmorshea rmorshea commented Feb 28, 2022

closes: #684

This may not be a perfect solution. I worry that doing this may have unintended
consequences. For example, what if someone wanted to have some sort of
auto-correct feature. Will setting the target value somehow overwrite
auto-corrections? From limited testing it seems to work fine, but that
testing was not extensive.

This may not be a perfect solution. I worry that doing this may have unintended
consiquences. For example, what if someone wanted to have some sort of
auto-correct feature. Will setting the target value somehow overwrite
auto-corrections? From limited testing it seems to work fine, but that
testing was not extensive.
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.

Input's onChange Event Handler Misses Key Strokes?
1 participant