Closed jason-capsule42 closed 1 year ago
This issue was caused due to the removal of code in this PR.
This PR was part of a major refactor of the related functionality. I feel that the miss was attributed to a missing test. We will want to look into how this feature was missed in the refactor and augment the testing scenario to ensure that this is not a problem in the future.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The correct required validity state is applied to the auro-input but the
auroInput-validated
event is never fired.