-
Notifications
You must be signed in to change notification settings - Fork 47.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use an ordered property list for inputs, fix some Chrome number input issues #7474
Closed
Closed
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
eaf986b
Store properties as a list
nhunzaker 5e92612
Remove mutation methods
nhunzaker f836654
Add property assignment test for similar value.
nhunzaker 2f5050e
No need to update value/checked on updateWrapper or have iOS/Android …
nhunzaker 5a8c422
Switch back to object config. Add priority field
nhunzaker 7bfcb06
No need to add forced update branch
nhunzaker 2032fc8
Do not remove mutation method. Keep change small
nhunzaker 762fca3
Use mutation method for value. Add test coverage for all states
nhunzaker 6238eec
defaultChecked chrome bug can be handled as mutation method
nhunzaker 3739426
Faster enumeration of ordered props
nhunzaker e8c77cd
Only order props for inputs
nhunzaker 4d54faa
Revert null assignment condition removal
nhunzaker 0495c8f
No need to prioritize defaultValue and defaultChecked
nhunzaker 1dfbd8c
Eliminate some white space. Add comment about order property.
nhunzaker cc54aa4
Place min/max ahead of value input prop order list
nhunzaker 0501c39
There must be a post mount wrapper
nhunzaker d39d919
Re-eliminate the postmount wrapper with a special defaultValue mutati…
nhunzaker 5d8c8ef
Be sure to update value attributes
nhunzaker 4e5ac47
Add test case for progress elements
nhunzaker File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
value
is shared by<progress>
(and some other tag?), so this seems like a no-go. A progress with null value must remove the attribute.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ya. Took care of that in #7359.
Hmm.. This PR is creating some extra noise for the input issue. Should I close this for now and resubmit after that settles?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah heck, I'll just bring it over while I'm thinking about it. That way things are at least up to date. Thanks for the prod!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added, and I brought over the
<progress>
test case from #7359 too. Though it re-introduces theinput[type="number"]
decimal place loss issue. Either way both PRs are synced.I don't feel awesome about this
value
mutation method, but with all of the mutations in one place, it's way easier to reason about the[type="number"]
issues on this branch. Curious if I'll get any inspiration shifting back here.