516037 - autocomplete changes the input's value to the case of a matching entry (FOO --> foo).

Status: RESOLVED DUPLICATE of bug 499649

(Toolkit :: Password Manager, defect)

Description

[tutufan]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090803 Ubuntu/9.04 (jaunty) Shiretoko/3.5.2
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090803 Ubuntu/9.04 (jaunty) Shiretoko/3.5.2

While trying to join IEEE at www.ieee.org, while creating an account, they require the desired username to be entered in all capital letters (stupid, yes, but not illegal).  If I try to enter an uppercase username that Firefox already has a lowercase cognate for, it will replace the uppercase username with lowercase.  There appears to be no way at all to enter the uppercase version.

Reproducible: Always



Expected Results:  
Firefox needs to fastidiously avoid case-smashing for completion boxes.  We live in a mixed-case world, and Firefox should support it.  In particular, if the user types in "ABCDE", Firefox should *never* correct this to 'abcde'.

Comment 2

[Justin Dolske [:Dolske]]

Hmm, this isn't actually a dupe.

The problem here seems to actually be in autocomplete code. If you type "USERNAME" in a field and hit tab (without selecting "username" from the autocomplete dropdown), we still get a DOMAutoComplete event, and the value of the text field has already been changed to the lowercase value. So it's been changed before password manager even gets around to looking at it.

It's a little odd that DOMAutoComplete fires, since a value wasn't actually selected. That does allow eliminating a tedious manual selection step (typing "username<tab>" and having the login filled is nice), but maybe that should be implemented as a special case, dunno... We already have a blur listener. [When then fires after the autocomplete event, so we stupidly run the formFill code again.]

But fixing this while preserving bug 499649 could be kind of messy... We'd need to add code to do case-insensitive matching in fillForm(), and decide if onFormSubit() should be case-insensitive too [ie, if we should offer to save the "new" login, or recognize it as the old login / password change.]

Another possibility would be to just special case the autocomplete code to not change the field value after a tab/blur. That might actually be best...