code-charity / code-charity/youtube

šŸ’”Customizable ā€œUp Next inā€ Autoplay Countdown Timer

Open
#3,553 2 comments 0 reactions 0 assignees View on GitHub

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. Image

⚬ 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.