fix(setValidity): Added support for setting ValidityState from a native input as Chrome #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ve input as Chrome allows this
|
Released in 0.1.9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Another Chrome inconsistency. Chrome allows you to call
setValiditywith aValidityStatefrom a native input, this fails in the polyfill.I found that
Object.keys()always returns an empty array when passed aValidityStateobject and spread syntax (...) does not work either. Iterating withfor...inworks though, so I added a step to ensure the input is an object to make sureObject.keys()and...works as expected.