03-23-2011 11:53 AM - edited 03-23-2011 11:54 AM
i found a workaround that can be used if you want to get the toolbar back but some of the things wont work (nortons needs to update them first):
a] Go to "about:config" (take away quotes) - click the box to say you know what your doing!
b] Right click and go to new and select boolean
c] type in "extensions.checkCompatibility.4.0" in the box but make sure you take away the quotes and then set it to FALSE
now after you restart it should show the toolbar.
remember that some things wont work right now but nortons will be releasing a patch. im okay with them testing it as long as they test it good. we know what happens if things are tested as much as they should be. ;]
03-23-2011 12:03 PM - edited 03-23-2011 12:06 PM
I just happen to think you're getting a little overblown with all this nonsensical defense of Symantec. I, for one, am not attacking Symantec in itself, only criticizing its apparent lack of a better PR department that could have grabbed this issue and treated it in a fashion worthy of Symantec's responsibilities just for being where it is in the minds and in the opinions of so many millions of faithful users all over the entire world! This is what I feel. And I think I already expressed this feeling before. Unless, of course, I'm getting it completely wrong and Symantec does not give a hoot about what its customers think and expect from it, which I believe is far from being the case.
I would just add to what I already wrote before that Mozilla does NOT ask us to pay anything for the right to use their product... Symantec does! Do you see any difference here?
Frankly, the more serious misstep from Symantec might not have been its late and somewhat jerky reaction to the issue at hand, but the lack of a serious attempt at a prompt, clear explanation for what really caused it to be caught at this certainly unpleasant juncture; a serious information about the steps it is taking (or planning to take) to remedy the situation; and a reasonable timeframe for it to happen. Had it done all this, as I think it should have, most of us would most likely not be here now, exchanging all these niceties an lauds among ourselves, would we?
Be it as it may, I do not think my assessment and my expectation is unreasonable and I wonder whether Symantec actually needs or even benefits from the kind of defense that some people have been throwing out around here.
03-23-2011 12:16 PM
Competition between browsers means that major new versions (as opposed to minor updates) of IE, FF and Chrome are all coming out within a relatively short period of time. Major changes within browser software probably also require major changes in security software to match. So keeping Norton/Symantec security products current with new browser releases probably requires a fair amount of development and testing work for Symantec programmers. When dealing with security issues, it is important that programming work be done right, and trying to rush or pressure programmers is not helpful in this regard.
Having said that, FF is a major browser with a large and well-established user base, not some obscure product occupying a minor niche. Based on FF download figures, there appear to be well in excess of 7.5 million active FF users. It has been public knowledge for some time that Mozilla has been working on a new version of FF. This should not come as any surprise to Symantec.
Users use FF, like other browsers, for a variety of purposes. These are not limited to casual recreational browsing or social networks. They also include engaging in online securities, banking and other financial transactions involving login security; performing paid research for professional, business or academic purposes, often using paid subscription services with login security; communication with members of Congress and other public officials; dissemination of information regarding public events; and the like.
For people using FF for financial transactions or professional research, the Norton Internet Security Toolbar, including the Identity Safe feature, is a significant productivity enhancement which is used frequently and rapidly comes to be relied upon. It may be the only place in which users record or keep track of their passwords. If it is disabled, users may unexpectedly find themselves locked out of online financial, research and other accounts, with potentially significant practical consequences.
While Norton has undertaken a project to develop a patch for Norton Internet Security with the goal of restoring the functionality of the NIS Toolbar and Identity Safe feature, Norton appears to have done so on an intermediate-term basis. Symantec has apparently scheduled completion and rollout of the NIS Toolbar and Identity Safe patch for FF4 for some time in early May. That is approximately six weeks, or more than 40 days, from now.
To a Symantec programmer tasked with figuring out how to make the NIS Toolbar and Identity Safe work again after Mozilla just released a major new version of FF with many changes from the prior version, six weeks may well seem like a very short time involving tight deadlines. To a user who has downloaded FF4 because it offers security improvements, however, only to find that the NIS Toolbar and Identity Safe are now disabled, six weeks may seem like a very long time indeed. That is particularly true for users depending upon FF for financial transactions, professional research or comparable functions.
It is understandable that Symantec staff might feel that somebody else created this problem. After all, things were just fine until Mozilla threw things into confusion by issuing a major new release of FF. Mozilla's website indicates, however, that something like 7.5 million people have already downloaded and installed FF4. Assuming that a substantial portion of those FF4 users are Symantec customers, it would appear that Symantec has a very major customer relations problem on its hands, one which, if not resolved, has the potential to cause long-term damage to Symantec's market share, corporate credibility and financial condition. This is the kind of problem which Symantec's senior executive management needs to consider as a very high priority, and address accordingly.
03-23-2011 12:38 PM - edited 03-23-2011 12:38 PM
Cheers (and 1 kurdos...) for a serious, well explained and very reasonable position like the one you just laid out. This is exactly the task I thought Symantec PR services should have promptly undertaken. And it's a pity, because we are, most of us at least, long time users of an excellent product they have been selling for decades, and we all sort of expected a little more diligent and savvy response, did we not?
03-23-2011 12:42 PM - edited 03-23-2011 12:46 PM
I just happen to think you're getting a little overblown with all this nonsensical defense of Symantec.
My NIS and Firefox are working OK. I'm sorry some users are experiencing problems.
Software compatibility issues are not limited to any one vendor. Free or Subscription based.
In a perfect world all software would be flawless, glitch-less, bug-less and 100% compatible.
Last time I looked.... the world ain't perfect.
03-23-2011 02:01 PM
Just installed Firefox 4.0 for the first time.
Noticed that there are no site safety icons with Google or Bing. Just the magnifier.
03-23-2011 06:28 PM - last edited on 03-23-2011 06:35 PM by Tony_Weiss
03-24-2011 04:07 AM
[...]Firefox 4:[...] As with every Firefox release, Mozilla made some changes to their interfaces that caused us to make changes on our side. [...]
Kudos to abhay!
THIS is the sort of information anxious customers need to be able to understand why they have to wait for a component that they are vitally dependent upon. This is also the first piece of information an anxious customer would EXPECT Symantec to give out when faced with complaints of delays, especially as there was contrary information circulating here some days back (implying Mozilla had not made any changes relevant to Norton toolbar for 5 months.). NOT giving out this information promptly is going to be interpreted as tacit admission that there really is no good defence for the delay, which will understandably make customers frustrated because it looks like Symantec isn't sensitive to urgent customer needs. I'm no PR pro, but all of this seems like very basic and very low cost PR, and I am frankly somewhat astonished at how hard it seems to be for many well-known companies (not just Symantec) to grasp this.
03-24-2011 06:00 AM - edited 03-24-2011 06:02 AM
I wholeheartedly subscribe, if I may, to every word of what you just wrote. Even for the kurdos, which I had already registered.
03-24-2011 06:37 AM
Was this the case (see link)?
Or is it found you can't rely on the mentioned freeze to that part of Firefox?