[Explain your issues, be concrete, what is wrong and why. Make sure that you explain yourself and the text is clear and understandable.]
Videos won't play in Odysee when JS Shield is on
[If you want to report a broken page, please fill in details. If you have different issue, some information might be irrelevant. Try to provide as much relevant information as possible]
Pages affected: [URL/all pages/URLs] odysee.com
JShelter Version: 0.11.1
Popup information (open JShelter popup on affected pages:
Modify
Detail tweaks of JS shield for this site
[Optional:]
OS: Debian 11 (stable) Browser: LIbreWolf 107 Other extensions that might affect JShelter behaviour: CanvasBlocker Canvas Blocker - Fingerprint Protect ClearURLS
[Fill in what you expected]
The video would play normally
[Fill in what happened]
The video doesn't play
[Have you tried another profile/browser/machine/OS?]
No
[Have you tried tweaking the extension, e.g. JS Shield (see the setup section above). Please try to chage settings for the triggered wrappers. Were you successful?]
Yes, disabling JS Shield makes the website work properly
[Was there any progress?]
[Other additional notes]
None
Thank you for reaching out! I bet this is an issue with the WebWorker wrapper. See the heading How can I fix videos if they fail to play or retrieve data in time? on the FAQ page. Does adjusting that setting according to those instructions fix the issue?
How can I fix videos if they fail to play or retrieve data in time?
Setting the WebWorker wrapper to Medium won't work, but turning it Off works
I have exactly the same issue with video playback on any Nitter instance.
@panosalevropoulos Did you try changing the setting for the WebWorker wrapper to Medium or Off?
@thomzane Yes, it works with the WebWorker wrapper turned Off. But I didn't know if it's the desired behavior, that's why I thought I'd comment.
Just updating that WebWorker (set to Medium or Strict) is making me problems when logging in to Proton Mail. I don't know if I should file another issue so that it can be tracked down better because I guess WebWorker protection is known to cause issues often
Looks like a duplicate of #80
Metadata Update from @polcak: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)