code-charity / code-charity/youtube
Opening in new tab doesn't apply settings (playback speed, fullscreen, autoplay) - clearing cookies fixes it for a time
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.6k
- Forks
- 996
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 7
Description
1. Bug Report:
⚬ BUG:
When opening a video in a new tab, it appears none of the settings in the extension will apply. But if i then from that video navigate to a different video, the settings will apply.
It will also apply the settings if i press i to open the miniplayer, and then press i again to go back to the full video player.
So it appears that the settings will apply when the player is "reloaded"?
⚬ Browser:
Chromium Version 123.0.6312.90
⚬ HOW:
Clear cookies, login, play a certain amount of videos (not sure about this step here because it sometimes happens after a couple of days and sometimes it happens the same day), open a video in a new tab, see the issue, clear cookies, login, the issue is gone.
⚬ Does the bug not happen when you log out of YouTube?
It appears that logging out does indeed fix this issue, so it appears to be tied to your account? maybe after x amount of videos watched on an account they load the player differently?
ctrl+u gave me this:
ctrl+u.txt
It may be related to #1851 #2012 and #1856
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 new-tab behavior in Chromium 123.0.6312.90 using the reported cookie, login, and navigation steps. Inspect ctrl+u.txt and compare the behavior with related issues #1851, #2012, and #1856. Done means playback speed, fullscreen, and autoplay settings apply when a video is opened in a new tab without clearing cookies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100