Dear NoScript developers,
This has been a very useful add-on, though of course it's hard for a layperson to diagnose problems.
I'm running the latest version of NoScript -- and the following problem has been ongoing.
I'm also running Firefox 3.6.13 Portable, Better Privacy, CookieSafe (with cookies cleared and allowed for CBC), and Abine Taco.
I'm scratching my head about Canadian Broadcasting Corporation's Radio 3 site, which streams great alternative music. I can enable all the scripts on the page, and still get nothing to stream. All I can guess is that there's a 3rd party streaming service that is being blocked, but I can't get the tray menu to display what it might be.
It may have something also to do with Flash, as I get that "update Flash" request quite often, but I assume that's not at issue in reality, asI have no trouble clicking on embedded YouTube clips to view them, and so on.
Here's the website:
http://radio3.cbc.ca/
Also note that I am prevented from streaming from artists' pages as well by clicking on the green arrows to the right of individual songs. Don't know if this is the same glitch. See this page, for instance:
http://radio3.cbc.ca/#/bands/Ladyhawk
Thanks for your insights.
Streaming radio appears blocked
Streaming radio appears blocked
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Ant.com Toolbar 2.0 Firefox/3.6.13 ( .NET CLR 3.5.30729)
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Streaming radio appears blocked
It works for me as soon as I allow cbc.ca.
It may be an extensions conflict. Could you try disabling all your extensions except NoScript, then Standard Diagnostic? I suspect Abine...
It may be an extensions conflict. Could you try disabling all your extensions except NoScript, then Standard Diagnostic? I suspect Abine...
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Re: Streaming radio appears blocked
Blocking Flash in NoScript?
If so, you'll also have a Blocked Flash object you'll need to allow (after allowing cbc.ca).
If so, you'll also have a Blocked Flash object you'll need to allow (after allowing cbc.ca).
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
Re: Streaming radio appears blocked
Oh yeah. My bad. NoScript works. The problem was the No Autoplay add-on. Just sits in the background most of the time and seems innocuous.
Does NoScript have a No Autoplay function? Should I just dump No Autoplay, or can you describe situations where I may want it?
Thanks again for the awesomeness of NoScript!
Does NoScript have a No Autoplay function? Should I just dump No Autoplay, or can you describe situations where I may want it?
Thanks again for the awesomeness of NoScript!
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Ant.com Toolbar 2.0 Firefox/3.6.13 ( .NET CLR 3.5.30729)
- Giorgio Maone
- Site Admin
- Posts: 9524
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: Streaming radio appears blocked
NoScript Options|Embeddings|Apply these restrictions to whitelisted sites as wella.k.a. wrote: Does NoScript have a No Autoplay function?
It's up to you, but IMHO you should.a.k.a. wrote: Should I just dump No Autoplay, or can you describe situations where I may want it?
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Re: Streaming radio appears blocked
Ok, thank you, Giorgio.
Could you amplify just a little more on this? I see so few Autoplays these days that I don't know what's NoScript's behavior and what's No Autoplay's behavior.
My concern is that I don't want Autoplays on Whitelisted sites -- unless I explicitly single out that site. On some Whitelisted sites, I see media objects being displayed when I load them (for instance, nytimes.com loads the top-line photos and displays the preview image for the video player further down the page).
I like this situation, but am concerned that any site I Whitelist has permission to Autoplay media. (nytimes.com doesn't autoplay the video object when I load the page, just displays the preview image, but it's a polite site, and perhaps has permission to play stuff if it wants.)
In the case of the CBC Radio 3 site, suppose it was Whitelisted, but I didn't want it to Autoplay. I don't see a way for NoScript to block the embedded objects in ONE particular Whitelisted site by using the setting that you pointed me to.
Would be worth it to have a separate layer of Whitelisting for already Whitelisted sites? That might give some users headaches. Perhaps to fine-tune this, I should just use the No Autoplay Whitelist too.
Unless I'm missing something about NoScript's behavior -- and No Autoplay's Whitelist is fully redundant.
Thanks!
Could you amplify just a little more on this? I see so few Autoplays these days that I don't know what's NoScript's behavior and what's No Autoplay's behavior.
My concern is that I don't want Autoplays on Whitelisted sites -- unless I explicitly single out that site. On some Whitelisted sites, I see media objects being displayed when I load them (for instance, nytimes.com loads the top-line photos and displays the preview image for the video player further down the page).
I like this situation, but am concerned that any site I Whitelist has permission to Autoplay media. (nytimes.com doesn't autoplay the video object when I load the page, just displays the preview image, but it's a polite site, and perhaps has permission to play stuff if it wants.)
In the case of the CBC Radio 3 site, suppose it was Whitelisted, but I didn't want it to Autoplay. I don't see a way for NoScript to block the embedded objects in ONE particular Whitelisted site by using the setting that you pointed me to.
Would be worth it to have a separate layer of Whitelisting for already Whitelisted sites? That might give some users headaches. Perhaps to fine-tune this, I should just use the No Autoplay Whitelist too.
Unless I'm missing something about NoScript's behavior -- and No Autoplay's Whitelist is fully redundant.
Thanks!
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Ant.com Toolbar 2.0 Firefox/3.6.13 ( .NET CLR 3.5.30729)