03-24-2011 07:39 AM
I wholeheartedly subscribe, if I may, to every word of what you just wrote. Even for the kudos, which I had already registered.
I just happen to think you're getting a little overblown with all this nonsensical defense of Symantec.
03-24-2011 09:59 AM
I’m OK with waiting for the FF4 changes, but I don’t understand why it took until yesterday for Symantec to explain what it’s doing. IMO, there really is no good excuse for it.
03-24-2011 11:48 AM
Well the firefox 4 is out, where's Norton Toolbar for it? Come on Symantec, Now I can't access many sites as I was storing passwords in identity safe. you say resolved yea right.
03-24-2011 12:47 PM
I'm waiting for this as well. When people purchase and pay for software it is only reasonable to expect that they are supported in these situations. The Firefox API has been frozen and ready for final development for the last 5 months. It's not reasonable to think it would take this long to port a toolbar. Please address this shortcoming in your development management and they're scheduling.
03-24-2011 06:25 PM
Was this the case (see link)?
Or is it found you can't rely on the mentioned freeze to that part of Firefox?
Several posts in this forum quote posts on the Mozilla support forum, where a statement is made that FF interfaces have been frozen for more than 5 months.
Historically FF maintained frozen interfaces, meaning they should never change, and will remain backwards compatible in newer FF versions. Starting with FF4, this is no longer true, every release can change interfaces, and code must be recompiled with every new release. See the section on Binary Interfaces.
With every FF release, Beta, RC, and RTM, we integrate the new SDK, re-compile against it, fix static breaking changes, re-start full regression testing , and fix any dynamically discovered bugs.
As late as Beta 9, released on 14 January 2011, interfaces were changed that broke our code.
As an example, see “Bug 609440 - make JSString::chars / JS_GetStringChars fallible”.
To reiterate what Abhay wrote in an earlier post; quality is extremely important to us, and we do our best to support new browsers, but we must fully retest all functionality with the RTM version of the browser.
In the case of IE9, Microsoft made the RTM version of the browser available to us and other ISV’s for testing in advance of its public release, in the case of FF4, we received the RTM build the same time everybody else did.
03-24-2011 06:54 PM
Thank you to Norton for eventually responding, albeit a little bit too late. I agree with other posts on here in that Norton should have commented sooner. The developers knew full well that their product was incompatible with FF4. They could have given us a heads-up by posting something here in the forum. At least that way we would have known what to expect.
I read the post a few times over, and not once does the word "sorry" appear in it. We pay your wages at the end of the day...
03-24-2011 10:59 PM
I want to throw my hat into the ring and say that I too was disappointed to find that the NIS 2011 toolbar wasn't up and running with FF4 on release day. I hope this will not take too much longer. Ironically, I read through this thread on FF4 but had to switch to IE9 in order to login and make this comment.
Hogwash to the legalese in the User Agreement. It's there strictly to cover Symantec's butt. The company should be more concerned with taking care of it's customers than having the lawyers play their games.
I'd also like to add that Symantec had an obligation to it's customers to at least have made a comment in this thread much earlier than page 8.
03-24-2011 11:51 PM
This issue with Nortons and Firefox 4 could have been prevented if the devs at Norton started working on the toolbar issues when FF4 was in beta!
Happens everytime with Nortons and FF!