Closed Bug 483572 Opened 15 years ago Closed 15 years ago

Norton Internet Security 2009 toolbar doesn't work in Firefox 3.5

Categories

(Tech Evangelism Graveyard :: English US, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: h.morf, Assigned: cl58.bmo)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)

Norton Internet Security 2009 toolbar doesn't appears and work in Firefox 3.1 b3 but it works in your latest version Firefox3.0.7 

Reproducible: Always

Steps to Reproduce:
1.I open Mozilla Firefox
2.the NIS toolbar doesn't appears
3.


Expected Results:  
the toolbar should appears and should work like what it does in Firefox 3.0.7

build configuration target
i686-pc-mingw32
Flags: blocking-firefox3.1?
Whiteboard: firefox
Whiteboard: firefox → Firefox3.1b3
Version: unspecified → 3.1 Branch
Component: Disability Access → General
QA Contact: disability.access → general
Report this to Norton but I think they will release an upgraded version with the final Firefox3.1
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
This is not INVALID, Matti, it's Tech Evangelism. We shouldn't be shipping Firefox 3.1 without NIS working. We have contacts there and are in touch. The problem is known (they reach into code internals which have changed) and being tracked.

This does block 3.1 IMO.
Assignee: nobody → english-us
Status: UNCONFIRMED → NEW
Component: General → English US
Ever confirmed: true
Flags: blocking-firefox3.1?
Product: Firefox → Tech Evangelism
QA Contact: general → english-us
Version: 3.1 Branch → unspecified
Whiteboard: Firefox3.1b3 → [blocking 3.5]
This would is a complete new policy for me.
The current Policy is that broken Addons should be reported the the Addon author and not to us. (like bug 475653 which is far more common)

A company like Norton doesn't offer fixed versions for every Firefox alpha/beta release and I expect that such addons are not working because of a failed maxVersiuon string and that they release a new version if Firefox3.1/3.5 final is out.
I don't think this changes policy, and I don't think a hard and fast policy can be written that will work. NIS is a popular third-party security tool on our most dominant platform, Windows. Shipping Firefox 3.1 without ensuring that the NIS toolbar works will put millions of our users at a disadvantage. We can't do that, so we need to track the progress.

Not the best way to do this, but it's the system we have.
Adding tchung: Tony, is Norton Internet Security on the list of plugins that QA looks at?
(In reply to comment #2)
> This does block 3.1 IMO.

The status whiteboard reads "blocking 3.5". Is it?
Flags: blocking-firefox3.5?
I'll block on this, but I believe that Norton's already disabled their toolbar for 3.5; assigning to myself.
Assignee: english-us → beltzner
Flags: blocking-firefox3.5? → blocking-firefox3.5+
Confirmed that they have their maxVer set appropriately; they're not going to be able to ship a patch automatically until later in the summer, but they have a hotfix up that we can point to.
Flags: blocking-firefox3.5+ → blocking-firefox3.5-
Summary: Norton Internet Security 2009 toolbar doesn't work in Firefox 3.1 b3 → Norton Internet Security 2009 toolbar doesn't work in Firefox 3.5
Whiteboard: [blocking 3.5]
Yes I have also found that the Norton Toolbar does not work with version 3.5. I hope Norton fixes this by the time version 3.11 stops being supported. The sooner the better. If Firefox would detect sites that require user id and password better Norton would not be needed. Firefox misses dozens of site to remember log info.
Not sure if this is a duplicate, but will post in case it is not: not only does Norton's Internet Security not work automatically in 3.5, but it won't load period. In 3.0.10 and before, it would not load on startup, but you could close FF and reopen it to get the Norton bar. V3.5 won't load the toolbar even after a reopening.  Norton still says it is working in the background, but having the toolbar allows Norton to do more and fill in fields, etc... pls fix...
I guess the question is, will this be fixed? The norton toolbar provides password memory and an id memory which is very useful. It also remembers passwords that Firefox wont. I run XP and Firefox 2.0 on my netbook and it works fine. I did receive a notice that Mozilla will no longer update 2.0
Not only doesn't the Norton toolbar show up in 3.5, allowing you to log into Norton's Identity Safe from there, even if you open Norton and log into Identity Safe there, 3.5 apparently blocks it from filling in the logons and passwords. This is a real stopper for me.
re: comment #14, Norton has stated that their fix, which addresses the compatibility issues, will be released into their update system on Aug 24. The hotfixes that Mike talks about in comment #9 can be downloaded from the following URLs:

Norton Security 2009
http://www.symantec.com/norton/support/kb/web_view.jsp?wv_type=public_web&docurl=20090630125147EN

Norton 360 v.3
http://www.symantec.com/norton/support/kb/web_view.jsp?wv_type=public_web&docurl=20090630130818EN

For a little more info, the Norton Community notice outlining the patch to NIS for Win7 compatibility, which also includes the toolbar fix:

http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=65000&jump=true
An update for Norton is needed for Norton extensions to work in Firefox 3.5.  You need to download this from http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=61120
With the previous comment with a link to an update, I am marking this as Resolved-Fixed
Assignee: beltzner → cl58.sumo.bugs
Status: NEW → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.