600630 - Norton Internet Security 2010 Identity Safe Won't AutoFill Logon Credentials

Status: RESOLVED INVALID

(Firefox :: Extension Compatibility, defect)

Description

[jmbellune]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C)

Prior to the 3.6.10 update, NIS 2010 Identity Safe would autofill my logon credentials at any of my Norton-remembered web sites.  Now it won't autofill or manually fill any credentials on any web site.

Reproducible: Always

Steps to Reproduce:
1. Install NIS 2010 with all of the default settings.
2. Open Firefox and navigate to a web page that requires a login and let Norton remember the credentials.
3. Navigate away from that web site and then return to it.
Actual Results:  
NIS 2010 does not autofill the credentials fields on the web page.  Prior to Firefox version 3.6.10, NIS 2010 *did* fill in the credentials.

Expected Results:  
Version 3.6.10 should let Norton autofill the login credentials.

Comment 1

[Tyler Downer [He/Him]]

Pleaes talk to norton. This is something they need to take a look at

Comment 2

[jmbellune]

Hi Tyler.  Thanks for responding.  We've got a chicken/egg scenario here.  Norton thinks that since their extension worked in previous versions that it was the update that broke their functionality.  Plus, because IE isn't affected, they're not exactly rushing to take a look at it.

I know that Mozilla probably won't want to devote resources to investigating this, but I would be grateful for any time at all that is spent troubleshooting.

Thanks.

Comment 3

[Tyler Downer [He/Him]]

Even if an update broke it, then norton needs to update their extension so that it works. It is not Firefox's responsibility to ensure that the 7000 addons out there all work correctly with ever version of Firefox. If there is a bug in FF that norton is running into then they should notify us, as they can tell us better than anyone else can what the bug is.  But, as there was only two changes in firefox 3.6.10(https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20status1.9.2%3A.10-fixed), and you say that this worked fine in 3.6.9, I think this is norton

Comment 4

[Tyler Downer [He/Him]]

And, IE usues a differnt type of extensions framework than Firefox, so just because it works in IE doesn't mean anything.