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
Manually editing Start and End times in the Time Conductor popup now fire validation on keystroke, rather than field blur. This has two bad UX results:
Time Field
Editing the time immediately shows an 'invalid date' error in the date input as the user deletes a character in the time inputs, and worst of all, jumps the input cursor into the date input, which is actually well-formed. The user will almost always type a bad number into the date field as a result, making it harder to correct the situation.
Initial state
Delete the '5' intending to change it to a '0' Note that the validation message points to the wrong input.
Input cursor has jumped into the date input. User's finger in slow-motion types a '0'
Date Field
Editing the date immediately shows an 'invalid date' error as the user deletes a character prior to typing a new one. Delete the '8' intending to change it.
Expected vs Current Behavior
This has become the "punish early" UI model of form validation, which is bad.
We should only be validating inputs when the user blurs out of an input in the popup, and we definitely should not be jumping the user's input cursor into a different field than the one they were working in.
The 'Invalid' message should point to the actual bad input.
Steps to Reproduce
Follow steps above.
Environment
Open MCT Version: 4.1.0-next / RC10
Deployment Type: localhost, server
OS: any
Browser: both Chrome and Firefox tested.
Impact Check List
Data loss or misrepresented data?
Regression? Did this used to work or has it always been broken?
Is there a workaround available?
Does this impact a critical component?
Is this just a visual bug with no functional impact?
Does this block the execution of e2e tests?
Does this have an impact on Performance?
The text was updated successfully, but these errors were encountered:
Manually editing Start and End times in the Time Conductor popup now fire validation on keystroke, rather than field blur. This has two bad UX results:
Time Field
Editing the time immediately shows an 'invalid date' error in the
date
input as the user deletes a character in thetime
inputs, and worst of all, jumps the input cursor into thedate
input, which is actually well-formed. The user will almost always type a bad number into thedate
field as a result, making it harder to correct the situation.Initial state

Delete the '5' intending to change it to a '0' Note that the validation message points to the wrong input.

Input cursor has jumped into the

date
input. User's finger in slow-motion types a '0'Date Field
Editing the date immediately shows an 'invalid date' error as the user deletes a character prior to typing a new one.

Delete the '8' intending to change it.
Expected vs Current Behavior
This has become the "punish early" UI model of form validation, which is bad.
Steps to Reproduce
Follow steps above.
Environment
Impact Check List
The text was updated successfully, but these errors were encountered: