-
Notifications
You must be signed in to change notification settings - Fork 6k
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
SeekBar id exo_progress accessibility #2278
Comments
It's deliberately not focusable. This is because the FF/RW buttons above it are focusable and can be used to seek more easily. TV devices often have controllers with physical FF/RW buttons, and these can also be used. That said, we should definitely make sure it works correctly if it is made focusable, which isn't currently the case. We may also consider making it focusable by default if this makes seeking in long duration content easier (I'm not sure whether it does or not). |
This isn't perfect because it performs seeks whilst the user is holding down L/R, rather than when they release it. Performing the seek on release properly looks non trivial, and would likely require extending SeekBar. Issue: #2278 ------------- Created by MOE: https:/google/moe MOE_MIGRATED_REVID=143440580
On the demo app's exo_progress, android focusable is set to false. This makes it unable to be controlled without touch screen.
I created my own UI with facusable set true. When using touchscreen, the progress moves, however when using the keyboard arrows, the seekbar moves, but it gets updated again to the same position.
The text was updated successfully, but these errors were encountered: