Closed Bug 1625402 Opened 5 years ago Closed 5 years ago

Username won't auto-fill from a saved login on the accounts.firefox.com initial log in screen

Categories

(Cloud Services :: Server: Firefox Accounts, defect)

Desktop
All
defect

Tracking

(firefox74 affected, firefox75 affected, firefox76 affected)

RESOLVED FIXED
Tracking Status
firefox74 --- affected
firefox75 --- affected
firefox76 --- affected

People

(Reporter: alice0775, Unassigned)

References

()

Details

(Keywords: nightly-community)

STR:
0. Make sure username/password for accounts.firefox.com are available in about:logins

  1. Open https://accounts.firefox.com/
  2. Click input field

Actual Results:
Nothing will happen.

Expected Results:
Master Password dialog should pop up if necessary.
Saved login email should suggest.

Email field has: <input name="email" type="email" class="email tooltip-below" autofocus="" placeholder="Email">
"Fill login" context menu option is also missing for this field.
Works fine for the password field on the second page.

We know we don't support multi-page login forms yet (bug 348941) but I believe this used to work since the password fields were present in the document but hidden. Can we go back to that behaviour so login autofill works again in Firefox?

Component: Password Manager: Site Compatibility → Server: Firefox Accounts
OS: Windows 10 → All
Product: Toolkit → Cloud Services
Summary: Won't auto-fill a saved email and password on a accounts.firefox.com → Username won't auto-fill from a saved login on the accounts.firefox.com initial log in screen
See Also: → 1476755

I don't see how this is relevant to bug 1476755. This is about the built-in password manager which does run on accounts.firefox.com.

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Severity: normal → S3

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Severity: S3 → --

I'm no longer able to reproduce this. In latest Nightly clicking on the input field gives me a dropdown of my saved logins.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.