code-charity / code-charity/youtube

Page stops responding if "Player size" is set to non default option

Open
#1,673 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Exemplary! 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

Bug Report:

BUG:

Web page stops responding when scrolling down past the player to description/comments etc if the setting "Appearance > Player > Player size" is set to anything but the default option "Don't change".

HOW:

  1. Change the setting "Appearance > Player > Player size" to "Full height"
  2. Close and reopen Chrome
  3. Navigate to a YouTube video
  4. Scroll down the page and observe that the page will stop responding. The tab must be closed and reopened to view the video again.

EXPECTED (/preferred) behavior:

  1. Change the setting "Appearance > Player > Player size" to "Full height"
  2. Close and reopen Chrome
  3. Navigate to a YouTube video
  4. Scroll down the page and be able to view description/comments etc without the page crashing.

Screenshots: See video here
Context: This only started happening recently for me, previously this was working fine.

Setup:

⚬ ImprovedTube Version: 4.9
⚬ Browser: Chrome Version 113.0.5672.64 (Official Build) (64-bit)
⚬ Settings: See settings here
⚬ OS: Windows 10

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 reproducing the issue in Chrome 113 with ImprovedTube 4.9, using the reported “Appearance > Player > Player size” setting and the linked video. Confirm that scrolling below the player becomes responsive again when the setting is reset to “Don’t change,” then use that comparison to identify the affected player-size behavior and verify it after restarting Chrome.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.