Properly invalidate if required attribute/property changes #546
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type: bug
The following has been addressed in the PR:
prettier
as per the readme code style guidelinesDescription:
Current
InputValidity
meta andvalidity
middleware do not invalidate when the required status of a field changes. This results in an outside trigger being required before the correct validity is captured.This change, which is breaking, takes the expected
required
value and compares it to therequired
attribute on theHTMLFormElement
node. If they do not match, it invalidates (same behavior as when the values do not match).