Merged
Conversation
DataTriny
force-pushed
the
android-range-info
branch
from
ede79ec to
9cbcae5
Compare
DataTriny
force-pushed
the
android-range-info
branch
from
9cbcae5 to
4b8239f
Compare
mwcampbell
approved these changes
Feb 22, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Allows reporting current value for slider, progressbars, spinboxes... TalkBack also does not send increment/decrement action requests if this is not set.
Chromium also only use the float range type even though Android has integer and percentage ranges. We could get a better user experience by using these but I can't find of a good heristic that would work all the time. We can revisit this later anyway.