Page 1 of 1

Status Bar Icons In Latest Nightly

Posted: Fri Apr 30, 2010 10:11 pm
by sabret00the
The status bar icon doesn't change to reflect the state of the page. It's always stuck on 'no scripts have been allowed'.

Re: Status Bar Icons In Latest Nightly

Posted: Sat May 01, 2010 5:43 am
by Giorgio Maone
It seems to work for me on Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.3a5pre) Gecko/20100430 Minefield/3.7a5pre.
Are you using latest (1.9.9.73) NoScript version?
Does Tools|Error Console show any error message?
Does the status change after you click on the icon or change the tab?

Re: Status Bar Icons In Latest Nightly

Posted: Sat May 01, 2010 5:59 am
by therube
20100430 is a very buggy Trunk build (due to a whole host of problems caused by Add-ons Manager changes).
See if reverting to yesterdays (FF) build restores your icon.

Trunk 2.1a go haywire today, 20100430
http://forums.mozillazine.org/viewtopic ... &t=1876345

Re: Status Bar Icons In Latest Nightly

Posted: Sat May 01, 2010 9:06 am
by sabret00the
Giorgio Maone wrote:It seems to work for me on Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.3a5pre) Gecko/20100430 Minefield/3.7a5pre.
Are you using latest (1.9.9.73) NoScript version?
Does Tools|Error Console show any error message?
Does the status change after you click on the icon or change the tab?
1/ Yes
2/ Only a bunch of CSS errors
3/ Not sure if I get what you mean with question three. The page reloads and the popup menu shows that things are blocked/unblocked, but the icon still displays the crossed out S meaning everything still looks blocked even though it isn't.

Re: Status Bar Icons In Latest Nightly

Posted: Sat May 01, 2010 9:11 am
by sabret00the
therube wrote:20100430 is a very buggy Trunk build (due to a whole host of problems caused by Add-ons Manager changes).
See if reverting to yesterdays (FF) build restores your icon.

Trunk 2.1a go haywire today, 20100430
http://forums.mozillazine.org/viewtopic ... &t=1876345
For me the trunk is fine. I've read a lot of whinging on the forums because apparently extensions that haven't been updated to use the new API don't work. God knows how that'd happen. I mean it's not like there aren't version checks in extensions for reasons exactly like this one. How dare Mozilla. I suggest they go back to the old API and lose ground in efficiency just to make impatient nightly testers happy.