The validateMethod will not run the code that generates any validity state when using the noValidate attribute on the auro-input unless the error attribute is used to force an error state.
However, the validate() method still runs and fires the event saying it validated. It just skips over the actual validation logic using an if statement.
The event should only fire when that logic is executed or the element has a custom error defined using the error attribute.
To Reproduce
Steps to reproduce the behavior:
Execute the input with the required and noValidate attribute set.
Describe the bug
The validateMethod will not run the code that generates any
validitystate when using thenoValidateattribute on the auro-input unless theerrorattribute is used to force an error state.However, the
validate()method still runs and fires the event saying it validated. It just skips over the actual validation logic using anifstatement.The event should only fire when that logic is executed or the element has a custom error defined using the
errorattribute.To Reproduce
Steps to reproduce the behavior:
requiredandnoValidateattribute set.auroInput-validatedExpected behavior
The
auroInput-validatedshould not fire