🐞Incomplete settings application (subtitles, audio) during internal YouTube navigation

Open
#4,308 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start by reproducing navigation from a channel video list to a video, then compare it with opening the same video directly. Trace how settings are applied when a video loads, especially subtitles, audio tracks, and volume; done means internal navigation applies the configured settings without incorrect or repeated reloads.

Written by the indexing model from the issue text.

Description

Bug Feature request good first issue help wanted up-for-grabs

I noticed a specific behavior: when I open a direct video link, the page initially loads with YouTube's default settings, then reloads after a second to correctly apply the addon's options.

However, if I navigate from a channel's video list to a specific video, the page doesn't reload. Because of this, only some settings (like volume) are applied, while others (like subtitles and audio tracks) remain at YouTube's defaults.

I believe the root cause of this issue is that navigating internally from a YouTube channel page inherently prevents the addon from fully loading or applying all parameters.

My suggestion: Could the addon be programmed to verify that all settings are properly applied whenever a video loads? If a mismatch is detected, it could force a single reload to ensure everything works correctly.

Note: The "YouTube No Translation" addon seems to have exactly the same problem, so I'm not entirely sure if forcing a reload is the best solution, but it's an idea.

Dominant language
JavaScript
Stars
4.6k
Forks
996
Avg merge
2d 15h
Merged PRs (30d)
7

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.

More from code-charity/youtube

All issues in code-charity/youtube

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.