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
Implement range input sanitization #21952
Closed
+92
−149
Closed
Changes from 1 commit
Commits
File filter...
Filter file types
Jump to…
Jump to file
Failed to load files.
Loading status checks…
Fix a range input test
It was setting the value to " 123" without setting a maximum above. Since the specs specifies 100 to be the default max, the value we'd get after sanitization would be 100, not 123. This fixes it by setting the value to something that is between the default min/max.
- Loading branch information
commit e3e47712cae745b3754e15da208630f3cca58357
| "testharness" | ||
| ], | ||
| "html/semantics/forms/the-input-element/range.html": [ | ||
| "209ce25306e02986238ae26fb6fdf38b0a26a500", | ||
| "f57c520b87ea8adceb7311ef8d642db5cc5fa6b8", | ||
| "testharness" | ||
| ], | ||
| "html/semantics/forms/the-input-element/required_attribute.html": [ |
ProTip!
Use n and p to navigate between commits in a pull request.
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.
Why use
98rather than123?