[RESOLVED] Media issue at youtube, fixed by reloading page

Ask for help about NoScript, no registration needed to post
Quest

Re: Media issue at youtube, fixed by reloading page

Post by Quest »

Nice work. Youtube does not work at all.
Mozilla/5.0 (Windows NT 6.1; rv:61.0) Gecko/20100101 Firefox/61.0
Quest

Re: Media issue at youtube, fixed by reloading page

Post by Quest »

Nice work. Now Youtube does not work at all.
Not to mention some other sites. I sure could make them work, but for a while I think to only use temporary allows, especially because new FF version is coming with all its surprises. But nevertheless something profound has happened, because old custom settings are not working.
Mozilla/5.0 (Windows NT 6.1; rv:61.0) Gecko/20100101 Firefox/61.0
Quest

Re: Media issue at youtube, fixed by reloading page

Post by Quest »

Maybe I was too harsh. I first did not notice that the <MEDIA> popup does not appear anymore so that's probably fixed.
Only thing that is left/new is that some pages, for example Youtube and Hotmail (=outlook.live) do not load at the first attempt but after F5 or simply going away and back all is well. (Using 10.1.9.2rc2).
Mozilla/5.0 (Windows NT 6.1; rv:62.0) Gecko/20100101 Firefox/62.0
Quest

Re: Media issue at youtube, fixed by reloading page

Post by Quest »

I'm impressed. This reloading page issue seems to be fixed in v10.1.9.6rc1.
As I may have mentioned earlier, this was not only Youtube's problem, but the same issue existed on some other pages too.
But now they seem to be working too!
Mozilla/5.0 (Windows NT 6.1; rv:62.0) Gecko/20100101 Firefox/62.0
bo elam
Senior Member
Posts: 208
Joined: Sat Oct 14, 2017 2:25 am

Re: Media issue at youtube, fixed by reloading page

Post by bo elam »

I have used versions 10.1.9.6rc1and 10.1.9.6rc2 for the last 4 days, and haven't experienced the Media issue in Youtube or any site. I have been using my W10, I ll update NoScript in my W7 later on today and report if I continue to experience the issue in that computer but as of this moment, the glitch appears to be fixed. :)

Bo
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:62.0) Gecko/20100101 Firefox/62.0
Post Reply