Greasy Fork镜像

[ SOLVED ] It's related only with my userstyle enable:
Youtube WideScreen (New Design Polymer)

I have adapted it to support your useful script.

But i have problem with your thumbnail results (but i have the same problem with the normal related thumbnail):
the first are not visible (no image, only tittle and another infos).
I thinks it's a problem of lazyloading.
Can you find a solution against that ?

Hey decembre,

Unfortunately I don't have any issues with lazy loading. Does the problem persist when you scroll?
If yes, It's probably another issue. Can you check the user console for script errors maybe.

Thanks for the reply:
With my userstyle , if i scroll down the related thumbnail (moved on the right side).empty thumbnail image stay blank (no image).
But if i hover them with the help on addon which preview on hover , i can see them.
Maybe it's my CSS, which restrict the height of the page...
The principal problem is for the 5 or 6 first and sometime some random after (a few).
When i scroll, they stay blank but the others are loaded...
The problem is around some events around scrolling and viewport?

Have you tested my userstyle?
I don't see something useful in console (but i am not coder...)
If i disable all userscript and my userstyle, all thumbnails are charged when i scroll.

I've installed your script and since I don't have a wide monitor it doesn't really work.
I can see the layout problem now, but it has nothing to do with my script (since the thumbnails also don't load with only your userstyle enabled).

I'm guessing that your css breaks the lazyload script. To find a solution you would need to reverse engineer the youtube js files... and I really don't want to do that. You'll also probably need javascript.

Sorry,
Cptmathix

Thanks, i understand;
:-)
But, seems i have found a solution by changing my CSS for line 137:
ytd-watch-next-secondary-results-renderer ,
#related.ytd-watch-flexy
Seems giving height to them solve my problem (no certain, i tested and it work...).
Now all thumbnails are visible.

Yes that fixed it :)