code-charity / code-charity/youtube
š”Customizable āUp Next inā Autoplay Countdown Timer
Open
Nobody has claimed this yet.
Feature request
good first issue
help wanted
up-for-grabs
- Dominant language
- JavaScript
- Stars
- 4.6k
- Forks
- 996
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 7
Description
⬠PROBLEM:
I want more time to review the āUp next inā preview before the next video starts. An additional 5ā7 seconds would make a meaningful difference for me. With the current default timer, I often donāt have enough time to decide whether to let autoplay continue or cancel it.⬠SOLUTION:
Add a setting that lets users choose a custom āUp nextā countdown duration when Autoplay is enabled (for example: 5, 10, 15, or 20 seconds, or a user-defined value within a reasonable range). This would give users more control without changing the default behavior for everyone.⬠ALTERNATIVES:
An alternative would be a menu setting with a generic toggle for āLonger Up Next countdownā that applies a fixed duration set by your team of developers based on what makes sense from a development stand point.⬠RELEVANCE / SCOPE:
Some users may not want additional settings clutter. This can be mitigated by keeping the default unchanged and placing the option under Autoplay settings.⬠CONTEXT:
//
Thank you!
| SHORT Table | (Summary) |
|---|---|
| Problem | |
| Solution | |
| Alternatives | |
| Scope | |
| Side effects | |
| Context |
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 locating the existing Autoplay and āUp next inā countdown entry points and their settings UI. Check the current timer behavior and relevant tests, if present; done means a user-selectable duration works while the default remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100