User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20110420 Firefox/3.6.17 ( .NET CLR 3.5.30729; .NET4.0C) Build Identifier: Unknown as FF 4 removed I use the HP ProtectTools Security Manager with HP Credential Manager (Fingerprint reader). This lets me use my fingerprint to log in to sites etc. Every time I visit a new site and record credentials, it records them and the next time I can login automatically or using just my fingerprint. This works fine with FF2 and FF3 up to and including FF3.6.17 but breaks with FF4.0.1. I am critically dependent on this Single Sign On software and have therefore had to regress to FF3.6.17 Reproducible: Always Steps to Reproduce: 1.Be using HP Credential Manager with FF3.6.17 2.Install FF4.0.1 3.It is broken (web pages not recognised for automatic sign on etc.)
That would be a problem for HP to fix. If they discover that it's caused by a bug in Firefox, then they will contact Mozilla of course. But at this moment, there's nothing to do here.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
I disagree entirely - the breakage was caused by FF4.0.1. - I very much doubt that HP will even know of the problem, and there's no mechanism for me to tell them about it apart from their "peer assistance" forums which HP hardly look at. The chances of HP looking at this is almost nil, and the solution IMHO lies with FF.
Status: RESOLVED → VERIFIED
There is nothing to fix for Mozilla. There is no API for fingerprint software and everything is done by the HP software which we can not fix if it's broken after some changes in Firefox.
I completely disagree. This isn't about fingerprints this is about the Credential Manager software being able to recognise the web pages with userid and password prompts. Something in Firefox has changed that is preventing it from working. This has worked OK with earlier FF, and all releases of IE from 6 to 9, so this is clearly a FF issue, not an HP one.
Mozilla isn't responsible for the HP Software, HP is. They have to analyze the problem and fix it. If they discover that it's due to a Mozilla bug, then they will notify us of course, but that is a totally different matter. You can argue about responsibility all you want, but since Mozilla does not have the source code of the Credential Manager (and probably not even that software/hardware combination to test), there's absolutely nothing (nada, zilch) that can be done. This is *really* a job for HP.
You need to log in before you can comment on or make changes to this bug.