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
When tabbing out of a valid field (and the field moves from isModified false => true), calls are made to the css handler that temporarily put it into an invalid state.
The changed that caused this was this one, where the function declaration order of the h_obsValidationTrigger and setError functions are reversed.
The symptom is that any triggers/hooks that listen for DOM changes or CSS changes will fire even though the user did nothing wrong. In the example, this is shown using a CSS transition, which causes a form flicker.
Why was the method order reversed in that other PR? Could it be changed back?
The text was updated successfully, but these errors were encountered:
When tabbing out of a valid field (and the field moves from
isModified
false => true), calls are made to the css handler that temporarily put it into an invalid state.The changed that caused this was this one, where the function declaration order of the
h_obsValidationTrigger
andsetError
functions are reversed.This is demonstrated in a simple JSFiddle here: https://jsfiddle.net/hlascelles/3Lz5ug8x/9/
The symptom is that any triggers/hooks that listen for DOM changes or CSS changes will fire even though the user did nothing wrong. In the example, this is shown using a CSS transition, which causes a form flicker.
Why was the method order reversed in that other PR? Could it be changed back?
The text was updated successfully, but these errors were encountered: