Greasy Fork镜像

Had to hide www.youtube.com###panels-full-bleed-container with uBlock to use the full width while watching VODs.

Can you tell me more about this issue? and how can i reproduce it? thanks

Can you show me the screenshot about the problem too? thanks

I found a similar bug here:

https://github.com/code-charity/youtube/issues/2074

Probably youtube doing youtube things, so yeah, check the new update (2.1.2) and let me know if it fixes the problem.

Had to hide www.youtube.com###panels-full-bleed-container with uBlock to use the full width while watching VODs.

Don't forget to remove this rule in your uBlock first.

Probably youtube doing youtube things, so yeah, check the new update (2.1.2) and let me know if it fixes the problem.

It didn't.

Please help me then :), send a screenshot of what's the problem and make sure there is no other extension or script that causes this problem. Unfortunately, I can't reproduce the problem you describe on my end, and this script does not even mess with the full width of the player.

Are you using ImprovedTube Extension and using live chat hidden feature?

Are you using ImprovedTube Extension and using live chat hidden feature?

Nope, these are what happen to be enabled atm, on this vod:

Are there any extensions you install besides these YouTube scripts?

Hey, is this problem still happening on your end on the latest version?
If this problem is still happening, can you make sure this script is what caused that problem?
Thanks.

Thank you tordenflesk. No clue how you figured this out but you seem to know scripting better than the author. Script is unusable without your contribution

Thanks for the info, @rokoe. So the issue is still happening, could you help me out? Could you let me know which browser and userscript extension you're using, and if there are any other scripts or extensions that might be affecting YouTube? I’ll look into finding a fix for this problem again. Thanks!

*Edit: Can you make sure the issue is actually caused by this script? Try disabling and re-enabling it to see if the problem still happens.

Can you try version 2.3.0, @rokoe? Hopefully it fixes the issue.