does not show the noscript submenu, whether from icon or the context menu, only accessible from the "options" button panel or the extensions menu, doesn't sound so much of a story, but it does bother especially on slower systems
Mozilla/5.0 (X11; ; Linux i686; rv:1.8.0.12) Gecko/20090423
Supported browsers: Firefox 1.5.0.6 and above, SeaMonkey 1.0.5 and above, Flock, IceWeasel, Minefield
Other browsers based on Gecko 1.8.0.6 and above might work, but are not tested.
Works for me on Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.0.14eol) Gecko/20080110 Firefox/1.5.0.12eol (.NET CLR 3.5.30729)
Is any error message displayed in the JavaScript Console?
Could you try Standard Diagnostic?
In all fairness you can only keep a software backwards compatible for so long. At some point, the user chooses to stay in the past, they will have to risk having problems. No?
~.:[ Lï£ê ï§ å Lêmðñ åñÐ Ì Wåñ† M¥ Mðñê¥ ßå¢k ]:.~ ________________ .: [ Major Mike's ] :. ________________
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 AdblockPlus/1.0.2 RequestPolicy/0.5.5 NoScript/1.9.2.1
I'd like to report the same problem with NoScript and FF 2.0.0.19 on Solaris 2.8 (and before anyone suggests to upgrade, yes, I know both are old versions, and no, I cannot upgrade). The popup menu from the NS icon (bottom right of window) worked up through NS version 1.9.1, but is broken in 1.9.1.2 and later.
This sounds like a minor annoyance, but it really becomes a big enough issue I'm sorely tempted to uninstall NS or just say fsck it and allow scripts globally. I'd really rather not do have to do that though, especially since NS 1.9.2.6 (the current version as of this posting) is claimed to work with "Firefox: 1.5 – 3.6a1pre"....
Right now, NS is the only extension I have installed. I moved my ~/.mozilla folder out of the way and created a new one, as if using FF for the first time. Then I installed NS -- it grabbed 1.9.2.6 of course. I then made a wild guess and installed 1.7.1 -- that worked ok. I then worked my way up to find the first version that didn't work -- 1.8.1 worked, 1.9.1 worked, 1.9.2 didn't, so I was able to narrow it down pretty quickly.
Are there any other diagnostics you'd like me to try?
Cheers!
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.8) Gecko/2009032608 Firefox/3.0.8
user wrote: Then I installed NS -- it grabbed 1.9.2.6 of course. I then made a wild guess and installed 1.7.1 -- that worked ok. I then worked my way up to find the first version that didn't work -- 1.8.1 worked, 1.9.1 worked, 1.9.2 didn't, so I was able to narrow it down pretty quickly.
This confirms the general impression that something bad happened in version 1.9.2.
Giorgio, are you being 100% open and transparent here?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090506 Shiretoko/3.5b5pre
GµårÐïåñ wrote:In all fairness you can only keep a software backwards compatible for so long. At some point, the user chooses to stay in the past, they will have to risk having problems. No?
Completely irrelevant statement that should not be made by a mod or whatever you are.
NS allegedly supports Fx 1.5. If not, then update the AMO.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090506 Shiretoko/3.5b5pre
therube wrote:Is it not possible that a bug crept in.
Yes, the 1.9.2 releases were a bit hasty, right?
Further cannot a mod, or whatever, make any comment that they want too. And guess what. Sometimes they'll be right. And sometimes they'll be wrong.
Some are more wrong than others. Maybe you need a discussion in the Metaforum (or offline) about the quality of the modification. NoScript is suffering not only from the May Day incident, but also from the forum activities.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090506 Shiretoko/3.5b5pre
@GµårÐïåñ, Lundholm:
please calm down.
1.9.2's release has been controversial, and one feature has been rushed up as Lundholm said, so this authorizes the suspect a bug crept in.
On the other hand, this is not the case (at least regarding the reports here), because both the major changes in 1.9.2 are triggered by precise post-startup events (i.e. activating the bookmark syncrhonization and visiting noscript.net) and do not affect the UI in any way.
Here we're seeing something different, and difficult to reproduce (as I said I tested on 1.5.0.12 and on 2.0.0.20 with no problem at all).
@user:
not sure, are you saying that the icon is not shown even in a clean profile?
The icon is shown, but clicking does nothing. In <1.9.1.2, clicking the icon brings up the "Temporarily allow...." menu (sorry, don't know what else to call it). In >= 1.9.1.2, I don't get the menu.
Again, this behaviour began with 1.9.1.2.....
Cheers!
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.8) Gecko/2009032608 Firefox/3.0.8