Click to Play?

Discussion of features in Seamonkey
Post Reply
User avatar
CMonkeyBloke
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Click to Play?

Post by CMonkeyBloke »

Has anyone tried the experimental click to play for plug-ins? Since I am having difficulties installing Flashblock. For anyone interested click to play is in ~ about:config ~ plugins.click_to_play ~ set 'false' to 'true'.
User avatar
CMonkeyBloke
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Re: Click to Play?

Post by CMonkeyBloke »

Anyone had any odd clashes with NoScript?
User avatar
therube
Posts: 21714
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: Click to Play?

Post by therube »

Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
User avatar
CMonkeyBloke
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Re: Click to Play?

Post by CMonkeyBloke »



OK thanks The Rube. Will do.
User avatar
therube
Posts: 21714
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Re: Click to Play?

Post by therube »

NoScript development build.

Code: Select all

2.5rc1
=======================================
x Fixed interaction with built-in Firefox's click-to-play causing
  infinite object activation loop (thanks al_9x for reporting)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
User avatar
CMonkeyBloke
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Re: Click to Play?

Post by CMonkeyBloke »

OK, thanks for the info therube. 8-)
User avatar
CMonkeyBloke
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Re: Click to Play?

Post by CMonkeyBloke »

OK, I've tried the development build with click-to-play & so far it is fine. One odd bug seems to be that the click-to-play won't run (on YouTube for instance) when clicked when the browser is first opened. This can be solved by simply reloading the page. I've noticed this behaviour more than once. I don't think it has anything to do with the development build of NoScript.
Post Reply