You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using inputs that aren't of type text, password or number, and having textUpdateMode set to onTyping, OnValueChanged event will only fire when the field loses focus (default setting).
Type on the email/telephone field, you'll notice the value is only logged after the field loses focus.
Expected behavior
I expected onValueChanged to fire on input fields of any type
Please complete the following information:
Browser: Brave
Browser version: 1.73.91
JS framework/library: React/Vanilla JS
SurveyJS version: v1.12.2
Device: MacBook Air M1
Additional context
4 years ago a related ticket was raised. While it seems fair to not allow all input types to trigger onValueChanged, I think there should be:
Documentation in the API Reference regarding "onTyping" mode working only for certain input types ("text", "password" and "number" per question_text.ts line 141)
An option to unlock onTyping mode for input types the developer chooses to (or for all).
This way you guys ensure the developer fully knows the risks/caveats of unlocking onTyping mode but there's a way to do it.
The text was updated successfully, but these errors were encountered:
yohanc3
changed the title
"text", "password" or "number" input types with OnTyping mode not triggering OnValueChanged event
"text", "password" or "number" input types with OnTyping mode not triggering OnValueChanged event on keystroke
Jan 2, 2025
Describe the bug
When using inputs that aren't of type
text
,password
ornumber
, and havingtextUpdateMode
set toonTyping
,OnValueChanged
event will only fire when the field loses focus (default setting).Steps to reproduce
CodeSandbox: https://codesandbox.io/p/sandbox/stupefied-tharp-95vhdc
Expected behavior
I expected
onValueChanged
to fire on input fields of any typePlease complete the following information:
Additional context
4 years ago a related ticket was raised. While it seems fair to not allow all input types to trigger onValueChanged, I think there should be:
Documentation in the API Reference regarding "onTyping" mode working only for certain input types ("text", "password" and "number" per question_text.ts line 141)
An option to unlock
onTyping
mode for input types the developer chooses to (or for all).This way you guys ensure the developer fully knows the risks/caveats of unlocking
onTyping
mode but there's a way to do it.The text was updated successfully, but these errors were encountered: