Password is erased on the page loading with autocomplete set to on

NEW
Unassigned

Status

()

Toolkit
Password Manager
4 years ago
4 years ago

People

(Reporter: Xavier OTTOLINI, Unassigned)

Tracking

({regression, site-compat})

34 Branch
x86_64
Windows 8
regression, site-compat
Points:
---

Firefox Tracking Flags

(firefox32 unaffected, firefox33- affected, firefox34- affected, firefox35- affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20140902030202

Steps to reproduce:

There are thwo inputs login and password. Infragistics Javascript library for JQuery allows to set validators.
The inputs are with the attribute autocomplete="on".
The user loads the web application login page.
He enters the login


Actual results:

The password is display as rounds and then is erased. The problem does not occurs on Firefox 31.


Expected results:

The password should not be erased and the user should be able to sign in without typing the password.

Comment 1

4 years ago
Can you provide a testcase?
Component: Untriaged → Password Manager
Flags: needinfo?(xavophonic)
Product: Firefox → Toolkit
(Reporter)

Comment 2

4 years ago
Created attachment 8483317 [details]
testcaseof the bug #1061762

The bug occurs when the user move the cursor to the password field with the tab key.
Flags: needinfo?(xavophonic)
Confirmed in 35.0a1 (2014-09-10), Win 7 x64

STR:
1. Enter user and password
2. Choose to remember in the pop-up
3. Clear the user/pass boxes
4. Enter the user and then press TAB
AR:
password appears, then quickly disappears
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression, regressionwindow-wanted

Comment 4

4 years ago
[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

[Tracking Requested - why for this release]:

Regression widnow(m-i)
Good:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0b5918ec6521
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140628031428
Bad:
https://hg.mozilla.org/integration/mozilla-inbound/rev/2f1356e9b56d
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140628111229
Pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0b5918ec6521&tochange=2f1356e9b56d

Suspect:
	fc701f3d06b2	Blake Kaplan — Bug 993197 - Asynchronize nsILoginManager::autoCompleteSearch. r=dolske
Blocks: 993197
status-firefox32: --- → unaffected
status-firefox33: --- → affected
status-firefox34: --- → affected
status-firefox35: --- → affected
tracking-firefox33: --- → ?
tracking-firefox34: --- → ?
tracking-firefox35: --- → ?
Keywords: regressionwindow-wanted → site-compat
tracking-firefox33: ? → +
tracking-firefox34: ? → +
tracking-firefox35: ? → +

Comment 5

4 years ago
In local build
Last Good: fb57f323afdc
First Bad: 2f1356e9b56d
Regressed by: 2f1356e9b56d	Blake Kaplan — Bug 949617 - Make the login manager work in e10s. r=dolske/mconley/mfinkle/jimm
Blocks: 949617
No longer blocks: 993197
(In reply to Xavier OTTOLINI from comment #2)
> Created attachment 8483317 [details]
> testcaseof the bug #1061762
> 
> The bug occurs when the user move the cursor to the password field with the
> tab key.

This testcase it really too large to debug -- 3MB of infragistics + jquery isn't something we can wade into. It would be helpful if someone familiar with the internals of those libraries can summarize what they're doing.

I strongly this bug is a WONTFIX anyway. We've made a number of changes over the last year to improve performance and responsiveness, which can subtly change the timing of exactly when we fill in fields. Sounds like one of these libraries is clearing out the password field for some reason, and it only happened to work before.
Taking in account comment #6, I am going to untrack it. If someone disagree, please let us know.
tracking-firefox33: + → -
tracking-firefox34: + → -
tracking-firefox35: + → -
You need to log in before you can comment on or make changes to this bug.