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
Improve handling of .invalid class for atomic groups.
After submit, .invalid is applied to invalid questions and groups within a form.
If an atomic group is valid at submit, the group is not classed as .invalid (this is correct)
If an invalid entry is made within the group, the question is classed as .invalid (this is correct)
If an invalid entry is made within the group, the group is not classed as .invalid (this is INCORRECT)
If an atomic group is valid at submit, the group is classed as .invalid (this is correct)
If an invalid entry is corrected, the question is no longer classed as .invalid (this is correct)
If all invalid entries are corrected, the group is no longer classed as .invalid (this is correct)
If an invalid entry is corrected, but invalid questions remain, the group is no longer classed as .invalid (this is INCORRECT)
The text was updated successfully, but these errors were encountered:
This is standard behaviour. If an invalid field is corrected, the .invalid class should be removed.
If an invalid entry is made again, the .invalid class is not restored until submit.
Alerts are handled correctly but .invalid class remains.
This may relate specifically to questions where the validity state is related to another field. For example, 'Card has expired' on credit card form where expiry is an atomic group composed of MM and YY fields. Fixing either field may correct the error.
set custom error on 2 fields within atomic group
submit form (invalid class will be applied)
clear the custom error on both fields, but only trigger change on one field
the field in the change event will be correctly updated, the other field will still have the .invalid class
Should the check validity onchange handler be invoked for every field within the atomic group?
(Make sure that does not cause an infinite loop!)
Improve handling of
.invalid
class for atomic groups.After submit,
.invalid
is applied to invalid questions and groups within a form.If an atomic group is valid at submit, the group is not classed as
.invalid
(this is correct)If an invalid entry is made within the group, the question is classed as
.invalid
(this is correct)If an invalid entry is made within the group, the group is not classed as
.invalid
(this is INCORRECT)If an atomic group is valid at submit, the group is classed as
.invalid
(this is correct)If an invalid entry is corrected, the question is no longer classed as
.invalid
(this is correct)If all invalid entries are corrected, the group is no longer classed as
.invalid
(this is correct)If an invalid entry is corrected, but invalid questions remain, the group is no longer classed as
.invalid
(this is INCORRECT)The text was updated successfully, but these errors were encountered: