-
Notifications
You must be signed in to change notification settings - Fork 15
YouTube scripts don't work on homepage #16
Comments
@ghajini I had the same issue on the FrontPage (subscriptions worked fine). I believe it was a list issue, as everything does work perfectly now :) |
I can reproduce this, but no exceptions are being thrown or logged so it's a little hard to identify where the issue is. |
@ghajini Please don't mention the nickname of gorhill on this repository. He doesn't work on the Edge version because he doesn't use Windows. |
It seems the following lists cause the issue:
The issue is that all some or all YouTube scripts seem to stop working. This includes lazy-load of assets and items. |
After many hours of trawling through YouTube's uglified code, I've discovered that the root cause of the issue seems to be that To replicate it inside YouTube:
Now you should either get an alert (eg, maybe a race condition meaning YouTube sets
|
Curiously this doesn't seem to be an issue if you load a video and then click back to the homepage; everything seems to init fine on video pages, and as long as you don't refresh the tab the homepage works fine. |
The Edge team is looking into the issue: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/9699196/ |
Update from one of the developers on the Edge team:
@gorhill, what are your thoughts about this? I don't know a lot about the core yet but I would assume this is fairly deep and challenging to override in platform. If I could it would still mean that iframe resources are loading (even if they're being hidden) which is less than ideal. My current best (but untested) idea for implementing a workaround extension-side is to detect the YouTube homepage URL in The alternative is to wait until this is fixed in Edge (Creators Update). It may or may not be backported to a cumulative update for the current release. Either way, waiting for an Edge fix will mean a delay in releasing the extension to the Windows Store. |
The issue needs to be more specifically described with all the technical details -- the description is too vague. Whatever solution there is might be different if I understand exactly the core issue with all the technical details. Not blocking I see this as a anti-user workaround. My stance with uBO is that it must be true to users. Silently doing the opposite of what its filters/rules say is the opposite of being true to users. uBO is a content blocker, not an "ad blocker", so its purpose is to block content, not to merely make "ads not visible" (which is what the proposed workaround does), something acceptable for an "ad blocker", but not for uBO. If no other solutions are possible, I rather not have uBO available until they fix such basic issue. uBO being true to users is more important than uBO being in Windows store. |
Thanks @gorhill. I agree on all points, I mainly wanted to cross-reference my thoughts with yours. I have found a workaround that addresses the exact issue, has no side-effects, and will be easy to remove once the Edge bug is fixed: Workaround for YouTube / window.onload issue. I'll leave it open for a day or so to give opportunity for feedback (optional), and then merge it for a future release. |
Workaround for YouTube / window.onload issue #16
Describe the issue
ublock breaking youtube pages.
cannot see preview images of youtube videos.
to see next youtube videos when i click "load more" nothing happens.
screenshot will tell you more
scroll down for seeing broken images
One or more specific URLs where the issue occurs
www.youtube.com
Screenshot in which the issue can be seen
Steps for anyone to reproduce the issue
1.go to youtube homepage
2.ublock breaking youtube pages
3.To see next youtube videos when i click "load more" nothing happens
4.screenshot will tell you more
5. click load more at bottom of page ,nothing will hapen(will not load next video)
Your settings
default settings
Your filter lists
Default filter lists + antiadblock killer + adblock warning removal list
Your custom filters (if any)
none
The text was updated successfully, but these errors were encountered: