512427 - Username & Password fields can not populated if autocomplete="off"

Status: RESOLVED WORKSFORME

(Toolkit :: Password Manager, defect)

Description

[Alex Pircher]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1

If autocomplete is set to "off" in the form-tag the password-manager stores nothing after submission. This can be circumvented manually by bookmarklets like https://www.squarefree.com/bookmarklets/forms.html#remember_password
Then the password-manager stores the submitted values.

When going to the login-page again Seamonkey 1 populated the fields even when autocomplete was set to "off", but Saemonkey 2 does not. You can not even populate the fields manually by clicking in the username-field.


Reproducible: Always

Steps to Reproduce:
1. Go to http://mail.yahoo.com/
2. Execute bookmarklet https://www.squarefree.com/bookmarklets/forms.html#remember_password
3. Save username and password in password-manager
4. Logout
5. Go to http://mail.yahoo.com/

Actual Results:  
Nothing

Expected Results:  
Automatical Population of username and password fields

Comment 1

[WADA:World Anti-bad-Duping Agency]

Have you searched B.M.O for bug of "autocomplete off" in bug summary, not only for open bugs but also for RESOLVED bugs?

Read Bug 63961(request for supporting of autocomplete=off), Bug 249035(request for capability to ignore autocomplete=off), and Bug 245333(request for keeping option of Fx 2/Sm 1 to ignore autocomplete=off).

Comment 2

[Alex Pircher]

Of course I have read resolved bugs too. Your mentioned bugs do not apply here
as ignoring autocomplete=off completely is not what I mean.

The behaviour of Seamonkey 1 is that storing of username and passwords if autocomplete=off can be overriden via a bookmarklet and is then used for populating the fields like described here:
http://kb.mozillazine.org/User_name_and_password_not_remembered#Using_a_bookmarklet

However, this behaviour is not working anymore in Seamonkey 2.

Comment 3

[WADA:World Anti-bad-Duping Agency]

Request to continue support for wallet.crypto.autocompleteoverride by Sm 2 was Bug 425145. (I thought Bug 425145 was already WONTFIXed. So I didn't search open bugs when I posted comment #1.)

Comment 4

[WADA:World Anti-bad-Duping Agency]

FYI. 
"alternate versions you can try" of the bookmarklet does do next.
(a) Clear onsubmit of any form in any frame on DOM.
(b) Set autocomplete=on on DOM, if autocomplete is defined by form in any frame.
You can use local proxy such as Proximation to remove autocomplete=off from HTML source or to change autocomplete=off to autocomplete=on, unless autocomplete=off is set by JavaScript code.

Comment 5

[Alex Pircher]

You are complexifying this, there exists also an extension which deletes autocomplete=off every time.

I have analyzed this a bit more:

* _fillDocument is called when a page load and there autocomplete is respected 
(http://mxr.mozilla.org/mozilla-central/source/toolkit/components/passwordmgr/src/nsLoginManager.js#1035), so an automatic population is not possible if 
autocomplete=off. This is the discussion about wallet.crypto.autocompleteoverride

* The problem seems to be the JavaScript function on http://mail.yahoo.com/ which sets the focus to the username-field at beginning. So populating the fields is only possible when clicking outside the field and then doubleclicking within the field.

As the Login-Manager of SeaMonkey 1 populated the fields automatically even when autocomplete=off it hadn't a problem with the focus set via JavaScript.

Comment 6

[Justin Dolske [:Dolske]]

This bug can go in two directions:

* Bug 362576 disabled autofill when autocomplete=off is present (but we still attach the popup, so you can manually select a login). This is intentional, so seeking to revert that is WONTFIX.

* In Firefox I get the autocomplete dropdown on mail.yahoo.com as soon as I start typing a matching login, or with a single click in the already-focused username field. If that's not working for you, it's probably a SeaMonkey problem. IIRC, you guys still use the xpfe autocomplete stuff, so it's possible that's not working right but the toolkit one is.

Pick one. :)

Comment 7

[Alex Pircher]

I have checked autofill when autocomplete=off already off, so I pick number 2 :-)

I have the same behaviour in the latest Firefox 3.5.2. I do not get the popup
if I start typing a matching login or click in the field. I have to click 
anywhere outside, then it is working. If JavaScript is disabled everything is
working fine, so the culprit seems to be the function which focuses the username
field at the beginning.

Comment 8

[Alex Pircher]

It is working in SeaMonkey 2.0 RC 1, so it seems that it has been fixed meanwhile. Closing this bug.