-
-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
black screen mystery bug #1759
Comments
I'm the dude in the top picture. My console when this happens: Hope that helps in some way. |
hi @NGTagger thank you so much for coming here & caring. The console doesnt show an error from our script. |
Just tried disabling both uBlock Origin, SponsorBlock, PrivacyBadger and 7TV (just to be on the safe side - and restarting the browser on another attempt, just to be sure) - no difference. Not sure it's a combination of things, as while trying your suggestion, I also tried with everything else turned off, so only your extension was turned on - the issue was still there. The only thing that stops/removes the issue, is disabling your extension. As soon as I turn it on; the issue comes back. |
thank you @NGTagger!
|
Also encountered this problem today. For me the fix was toggling the "Forced theather mode" off from "Apprerance -> Player" setting list. |
-- Can you log out? (or use incognito window) (maybe YouTube is testing a new version while you are logged in) Tried that. No difference. -- Did you open the console when/before the player was black? (then hopefully we'd see an error. Btw, maybe i should have said already, you can also run ImprovedTube alone, in an incognito window. Can activate it at chrome://extensions I opened up the console when the player turned out to be black/empty/void. -- Can you export your ImprovedTube setttings? Added my export. -- Does this happen witth Theatermode only? It reliably happens with "Forced Theater Mode", sure - but turning it off, doesn't guarantee that it doesn't happen again. Just makes it a bit more "random". I've found a little "workaround" though. |
thanks! @NGTagger couldn't reproduce it yet interesting:
(
yet i assume it it happens in existing sessions, too? (#1750 hints that, when restoring a browser session, then our extension might not be able to access the data tags at the start of the DOM. ) ) |
hi guys! Please help fixing this bug soon through testing the previous two versions linked above we especially still need to know if it really sometimes happens without "force theater mode" (like @NGTagger said) (which migh be another reason) and since when this one happens |
I'm having this problem too it happens on all 3 pcs chrome and edge and for me it's really consistent. The steps I'm able to replicate the bug: No ads popped up whether I'm logged in or not while I was testing so don't know if ads will affect it |
ok, should've fixed this earlier. |
…was defined var() also takes a 2nd value as an optional backup @HanzCEO @Fulgar @jarrodsmeyers
…was defined var() also takes a 2nd value as an optional backup @HanzCEO @Fulgar @jarrodsmeyers
hopefully they tell us their settings.
The text was updated successfully, but these errors were encountered: