03-24-2011 11:19 PM
I am running Windows Vista Home Basic, have Norton 360 v5.0 and just upgraded to Firefox 4.0. Since the upgrade, Identity Safe will no longer autofill any login information, nor does it ask me if I want to add new logon information to Identity safe. I checked "manage logins", and the data is appears to be stored correctly. Any ideas on what is going on or how to fix this?
03-25-2011 12:20 AM - edited 03-25-2011 12:21 AM
HI fisherka,
Welcome to the community!
Our developers are working on fixing some compatibility issues wiith FF4. Here is the link to the announcement.
http://community.norton.com/t5/Norton-360/Norton-c
Let us know if you need further assistance.
-Venkat
Venkat Jammalamadugu
Norton Forums Administrator
Consumer Products and Solutions
Symantec Corporation
03-25-2011 08:10 AM
fisher,
Norton are always very conservative in what they say in advance about "when" so I think you can take it that Norton, to say nothing about us users, hope that fixes will be available sooner than indicated in the announcment Venkat refers you too.
From other Norton Staff (Names in Red) posts in the forums some other problems with FF4 have already been fixed.
I don't use Identity Safe myself so I don't know exactly how it is supposed to work but in the interim is there no alternative route to carry out its functions than via the toolbar?
03-26-2011 02:11 PM - edited 03-26-2011 02:14 PM
Here's what I find interesting...EXTREMELY interesting, in fact...about this whole situation. First, let's go back to when Firefox 3.5 was released. Symantec went through the exact same thing, except with one major difference. With the upgrading of Firefox, from 3.0 to 3.5 (June 2009), Mozilla didn't give any advance warning to those (individuals, as well as companies, such as Symantec) writing various APIs (aka "plug-ins") for Firefox. The result, as you can guess, if you didn't experience this for yourself when it happened, is that there were a number of plug-ins that no longer functioned with the newly-released Firefox 3.5. Thankfully, the programmers of these APIs (again, companies & individuals, alike) came to the rescue in a reasonably timely manner, and the more useful of them were restored to full functionality.
Fast forward to today, with the upgrading from Firefox 3.6.6 to 4.0, we, essentially, have the same problem. Whereas Firefox 3.0 used the Gecko 1.9, which was upgraded to the Gecko 1.9.1 engine in Firefox 3.5, Mozilla has done the same thing here, upgrading to the Gecko 2.0 engine with the release of Firefox 4.0. There are a number of APIs out there that no longer function, although far less than what happened in June 2009, and for a good reason. This time around, Symantec notified API programmers (once again, companies & individuals, alike) that major changes were taking place. Not only that, but they made such notifications five months in advance of the release of Firefox 4.0.
If you consider the fact that, this time around, the great majority of plug-ins for Firefox had already been updated to work with Firefox 4.0, this leads to me to believe that, for the majority of that time, Symantec's programmers have been sitting on their arses, essentially doing nothing. If others, including Google & Skype, can write updated API within that five month periods, allowing them to work with Firefox 4.0, then why in the world wasn't Symantec able to do the same thing? While on the phone with someone from Symantec's tech support (or, what I would, more realistically, call tech anti-support, since they guy was a complete idiot, and couldn't even answer half the questions I was asking...that's what you get, Symantec, for outsourcing your support to countries such as India), I asked the guy, and the best response he was able to come up with way, “They are working on it.” When I asked him for an approximate release date, he had not the slightest clue. This, my friends, is the quality of programmers & support technicians Symantec now hires. I have used Norton products for a great many years, but, when my current subscription is close to expiring, I am going to serious consider, and research, alternatives from other companies. Symantec has lost their “touch”, and deserves to lose business. ![]()
03-26-2011 03:04 PM
Thanks for your honest feedback. I really should have done my homework before I upgraded. I guess now I will have to wait on Norton for their fixes.
03-26-2011 03:05 PM
Thanks so much for everyones feedback. At least I know what is going on now.
03-26-2011 03:08 PM
Thanks for sending the link to the announcement. I sure hope all goes as planned, and the fixes are in place sometime in May as planned. At least I now know what my problem is.
03-26-2011 03:41 PM
Actually, there's really no reason to "wait". You can do what I, and many, many others have done, at least for now. Uninstall Firefox 4.0, download the Firefox 3.6.16 installer (http://www.mozilla.com/en-US/firefox/all-older.htm
03-26-2011 08:33 PM
Thanks. If I go back to 3.6.16, will I lose all of the login information that is curently saved in 4.0?
03-26-2011 08:36 PM
The link you provided does not work. Would you check it and repost. Thanks!
