But I did see it work a few times before where it didn't in 2.28, weird.See below for security related patches released Between 09/01/14 and 09/30/14
FIREFOX FOR MAC 32.0.3 FULL
I know that's not a good solution but does that work?ĭoes NoScript (or any other https served file, for that matter) download fine in a clean profile?ĮDIT Worst case scenario, do you have a full Time Machine system backup from before these issues started?ĮDIT2 Just updated NS dev build, and had to click the link twice, so actually looks like that issue is not totally fixed in SeaMonkey 2.29.1. (If you can't connect via that https link, try changing the protocol to http or ftp.) Then, if that doesn't fix it.Īnother possibility might be to try to use the "Save Link As" context menu entry, then drag the NoScript add-on you downloaded into the Firefox window.
FIREFOX FOR MAC 32.0.3 MAC OS X
Wait, what? How can you check for updates to NoScript via the Add-ons Manager if you deinstalled NoScript?Īs another Mac OS X Lion user, I can tell you that until I upgraded from SeaMonkey 2.28 (like Firefox 31) to SeaMonkey 2.29.1 (like Firefox 32.0.3), I had to click on many XPIs twice to get them to download, and even then I had to be careful what I did or the XPI wouldn't install and the UI would be totally messed up.ĭelete Firefox.app and reinstall from a fresh. It was v2.6.8.35, and yet, when I clkd on Check for Updates using Firefox/Add-ons Manager/Extensions, including NoScript v2.6.8.35 RxDDude wrote:I "Removed" NoScript from my Firefox Add-ons. No problems with updating Extensions in Firefox on my Mac.
:max_bytes(150000):strip_icc()/001-how-to-use-firefox-for-mac-4588443-68cb18d149a24b1c812e4a94cc4790cb.jpg "firefox for mac 32.0.3")
FIREFOX FOR MAC 32.0.3 UPDATE
I never had this problem before Apple Security Update 2014-004,or with Firefox v2.6.8.43 on my Windows 8 machine. Is this behavior, now repeated about a dozen times tonight, the expected thing? Is there an about:config key that I can fix, for a workaround. The current time is 9/30/14 4:22 AM.Ī similar result came out when I tried to get NoScript via, only, the tab cited that domain, and when I pushed into the security glitch, it named the mozilla domain as the source of the errors. " The certificate expired on 4/6/13 8:32 PM. " The certificate is not trusted because no issuer chain was provided. The tab changed to say, "The add-on could not be downloaded because of a connection failure on ." A little further exploring work-arounds produced a security glitch page, and expanding the "Technical details" on that page revealed that Firefox had this complaint: "Firefox prevented this site () from asking you to install software on your computer." so I clkd on the button labelled, "Allow". When I tried to get NoScript v2.6.8.43 from the big, green Install button on the webpage showing in the browser's location slot, Firefox first put down a small tab below the bookmarks bar, saying approx. I had not used this Mac (OS X 10.7.5), since Apple's Security Update #2014-004 was installed, last Saturday night. It was v2.6.8.35, and yet, when I clkd on Check for Updates using Firefox/Add-ons Manager/Extensions, including NoScript v2.6.8.35 along with my ~13 other Extensions + 2 Plugins, the search reported, No updates found. I "Removed" NoScript from my Firefox Add-ons.
Helpful suggestions are requested, and will be received with gratitude, rather than attitude.
0 kommentar(er)
