QuantumBadger / QuantumBadger/RedReader
[request: accessibility] disable or make static loading spinners when device animations are disabled
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
When loading most posts/comments, images, or videos, an animated spinner is displayed, even if the "Remove animations" device-level accessibility setting is true and the window, transition, and animator duration scale developer settings are "Animation off" (0)
examples:
https://github.com/user-attachments/assets/9fe3bcfe-4aff-4e4f-9807-ba99b2951bf4
Ideally, according to one of the above settings or a new/existing RedReader setting, these spinners would be removed entirely, or replaced with a static indicator (for example, the "LOADING..." in the second part of the video)
in some other limited cases, it seems RedReader already uses a static load icon instead:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the loading spinners for posts/comments, images, and videos with Android animations disabled, then locate the implementations that differ from the existing static load icon. Determine which device or developer setting should control them and verify that the affected indicators are disabled or static while normal loading still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- accessibility, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100