Properly invalidate if required attribute/property changes by KaneFreeman · Pull Request #546 · dojo/framework
Type: bug
The following has been addressed in the PR:
- There is a related issue
- All code has been formatted with
prettieras per the readme code style guidelines - Unit or Functional tests are included in the PR
Description:
Current InputValidity meta and validity 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 the required attribute on the HTMLFormElement node. If they do not match, it invalidates (same behavior as when the values do not match).