SeekBar id exo_progress accessibility #2278
Labels
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). |
ojw28
added a commit
that referenced
this issue
Jan 4, 2017
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://github.com/google/moe MOE_MIGRATED_REVID=143440580
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: