Multiple Authors
	Description • 5 years ago • Edited

[OS:]
All

[Versions tested upon:]
53.0a1 20170111030235
52.a02 20170111004018

[Description:]
Having 2 or more saved passwords, first time that you call in a new tab the login form directly (w/o redirect) autocomplete/autofill/insecure warning will not be displayed.

[Steps:]
1. Create new profile.
2. Open http://imgur.com/login or https://github.com/login .
3. Save at least 2 user/passwords.
4. Close the tab, Open a new tab.
5. Input  http://imgur.com/login or https://github.com/login

[Actual Result:]
No autofill dropdown is opened. Although the username is focused, clicking in it or writing in it will not trigger neither autocomplete nor autofill.
Additionally, in the case of http the warning will not be shown either.

[Note:]
Switching the focus away will return the normal functionality.
Accessing the login pages from the redirect will again display the normal functionality.

	Tanvi Vyas[:tanvi]
	Comment 1 • 7 years ago

I created a new Nightly profile on Mac OSX.

Went to http://imgur.com/login.  Username field is autofocused.  I observed warning in username and password field.  Saved a bogus login (test1, test1).
Saved a second bogus login (test2, test2).
Closed tab
Go to http://imgur.com/login in a new tab.  Username field is autofocused but dropdown doesn't appear.  Password field has dropdown.  Switching back to username field, it shows drop down.

Note that if you try this with a new window instead of a new tab, the drop down does appear right away.  Also, if you open a new tab and navigate it somewhere else first (ex: google.com), then go to http://imgur.com/signin, the drop down will appear right away.  Same issue on github.

Dropdown is missing on username field for brand new tabs only.

Maybe this has something to do with the meaning of first focus on a new tab?

	Matthew N. [:MattN]
	Comment 2 • 7 years ago

I suspect this is caused by attachToBrowser happening too late. DOMContentLoaded seems too late to me since a focus could have already happened I think. Either move attachToBrowser earlier or have AttachToBrowser check if a relevant field is already focused.

https://dxr.mozilla.org/mozilla-central/rev/1d025ac534a6333a8170a59a95a8a3673d4028ee/toolkit/content/browser-content.js#1471-1482

	Pulsebot
	Comment 6 • 5 years ago

Pushed by mozilla@noorenberghe.ca:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c5219b2bbf2b
Check if a relevant field is already focused when attaching autocomplete. r=MattN
https://hg.mozilla.org/integration/mozilla-inbound/rev/5e4f3a3033e9
Add a test that confirms inputs that are focused before FormFill has been attached still have their autocomplete popup. r=MattN