Page 2 of 2

Re: Problem at cbssports with NS build 10.1.9.2rc1

Posted: Thu Sep 06, 2018 12:21 am
by bo elam
skriptimaahinen wrote:
So it looks like you just need to allow more domains, but since you said that even using "Disable restrictions for this tab" does not help, it could be something else.
Thanks to the insight you (and Barbaz) gave me I found whats going on and fixed my problem. First of all I had to untick "Always use private browsing mode" in Firefox Options. Look at picture. That allowed facebook.net to load, otherwise it wouldn't load. Amazing :).

https://imgur.com/a/NKquZY5

Also, to fix the issue now we need to allow facebook.com and facebook.net when as of two days ago two we didnt have to. This is new at cbssports. Hopefully they wont make more changes for a while. So, I ll be temporarily allowing those 2 domains when I visit the site.

https://imgur.com/a/einziHp

@barbaz, you can mark this thread as Fixed.

Bo

Re: Problem at cbssports with NS build 10.1.9.2rc1

Posted: Thu Sep 06, 2018 12:26 am
by bo elam
therube wrote:Just what part did we miss?


New Profile
Load https://www.cbssports.com/nfl/news/nfl- ... -top-spot/
Video Plays

Tools | Options | Privacy & Security -> Tracking Protection ---> ALWAYS

Reload https://www.cbssports.com/nfl/news/nfl- ... -top-spot/

Video Fails


NoScript is not involved, period.
Now if you use NoScript, the video still works - after you allowed needed domains AND assuming you don't have Tracking Protection enabled (or some other blocking - other then NoScript) going on that cbssports does not like.
Read my previous post so you understand what was going on, and forget about it.

Bo

Re: Problem at cbssports with NS build 10.1.9.2rc1

Posted: Thu Sep 06, 2018 1:18 am
by therube
If you were using Private Browsing, by default, Tracking Protection is enabled in Private Browsing.
Tracking Protection is the crux of the issue.

Once that is taken care of; running outside of Private Browsing, &/or adjusting Tracking Protection settings - as needed, then it is a matter of getting your other blockers to work with your website. And in this case, that blocker happens to be NoScript.