HTTPSB menu not reachable in some rudely restrictive popup browser windows (aka "pop-up media player won't play") about httpswitchboard HOT 9 CLOSED

Problem is the site itself: it fails without the extension with everything allowed, and also in Firefox. The site tries to get http://mediaplayer.yahoo.com/js?ver=3.5.1, but this fails.

EDIT: By the way, the "Listen live" button in the center of the page didn't work for me, I had to use one of the two buttons "On air Listen Live" on the right side, hence I thought the problem was the site.

from httpswitchboard.

Ok, I could make the player open in Firefox finally, after disabling NoScript. Investigating.

from httpswitchboard.

Ok, problem is that popup browser window tries to access http://player.streamtheworld.com/, but then HTTPSB popup menu is not available in this popup window, so it is not possible to see and whitelist player.streamtheworld.com.

Entering the address http://www.teamradio.ca/live/music-player/index.html of the popped up browser window in a new tab in the original browser window (not the popped up one) allows access to HTTPSB popup menu, so you can whitelist streamtheworld.com (including the plugin and frame column) which is sort of a workaround for now (padlocking this whitelisting will make the workaround work for future use of the site.)

Now I have to investigate what is the best solution for when a site uses a pop up browser window with restricted interactions.

from httpswitchboard.

OK just to be more clear about the workaround, here is a no-rambling version:

• Enter http://www.teamradio.ca/live/music-player/index-1410.html in a new tab in the browser
• Whitelist teamradio.ca.
• Whitelist streamtheworld.com.
• Whitelist plugin for streamtheworld.com if strict blocking is on.

Don't forget to make these whitelisting permanent. From then on, you should be able to play the radio in the popped up player the site launches, now and in the future (HTTPSB blocks a whole lots of other useless stuff in that popped up window).

from httpswitchboard.

I renamed the issue in order to be more accurate about where is the problem.

from httpswitchboard.

Thank you for your help and efforts, gorhill! It actually works fine with NoScript in Firefox because NS puts itself (for lack of a better description) in the media player pop-up window. Thanks again!

from httpswitchboard.

You are right, NoScript works despite the restrictive popup. The fact that the "Listen Live" button in the center of the teamradio.ca page (not the popup one) didn't work made me think NoScript also had a problem. I didn't revise my findings after I figured the other button to launch the play worked. These NoScript placeholders is one of the best feature of NoScript, and I am seriously thinking into borrowing the idea, although at this point I have no idea of the feasibility (meaning I don't know if there is any roadblock in chromium API). I will open an issue to remind me to work on this very useful enhancement.

from httpswitchboard.

Your workaround corrects the issue. Thanks! Will be sure to post other issues and feature requests. Hope to see an export/import of whitelist/blacklist entries some time. Your work is appreciated.

from httpswitchboard.

Same as #41

from httpswitchboard.