Closed Bug 1852236 Opened 3 years ago Closed 3 years ago

New logins added manually from about:logins page are not synced

Categories

(Firefox :: Sync, defect)

Desktop
All
defect

Tracking

()

VERIFIED FIXED
119 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox117 --- unaffected
firefox118 --- unaffected
firefox119 --- verified
firefox120 --- verified

People

(Reporter: oardelean, Assigned: enndeakin)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Notes

Found in

  • Firefox 118.0b6;

Affected versions

  • Firefox 118.0b6;
  • Nightly 119.0a1;

Tested platforms

  • macOS 12;
  • Windows 10;
  • Ubuntu 22;

Affected platforms

  • macOS 12;
  • Windows 10;
  • Ubuntu 22;

Unaffected platforms

  • N/A;

Preconditions

  • Valid credentials for an Fx Account.

Steps to reproduce

  1. Create a new profile, for example profile A.
  2. Navigate to about:logins.
  3. Log into the Fx account. ( It’s easier to test if the login page is empty, or has fewer logins)
  4. Manually add one or two new logins from the about:logins page.
  5. Sync Now on profile A.
  6. Create a new profile, for example profile B.
  7. Navigate to about:logins on profile B.
  8. Login with the same account from step 3 on profile B.
  9. Sync Now on profile B.

Expected result

  • The newly added logins in Step 4 from profile A should be synced onto profile B.

Actual result

  • Logins do not sync.

Regression range

Regressed by: 1846036
No longer regressed by: 1846334

Set release status flags based on info from the regressing bug 1846036

:enndeakin, since you are the author of the regressor, bug 1846036, could you take a look?

For more information, please visit BugBot documentation.

Assignee: nobody → enndeakin
Status: NEW → ASSIGNED

:neil deakin can we consider backing this regressor out from beta for Fx118?
We are in the final week of beta, or will this land soon and request uplift?

Pushed by neil@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c77f534dc9b9 treat null string formActionOrigin values as not present in certain cases, also restores some checks of formActionOrigin that got lost, r=credential-management-reviewers,sgalich
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch

(In reply to Donal Meehan [:dmeehan] from comment #3)

:neil deakin can we consider backing this regressor out from beta for Fx118?
We are in the final week of beta, or will this land soon and request uplift?

Our last beta is tomorrow, are we OK to ship 118 with this regression or should we uplift the fix that landed yesterday?

If the beta is that soon, would it be easier/safer to back out 1846036? That bug is just a cleanup patch and isn't an important change.

Flags: needinfo?(enndeakin)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 3 years ago → 3 years ago
Resolution: --- → FIXED
Flags: qe-verify+

Issue is verified as fixed on Firefox 119.0b2(build ID: 20230927091517) and Nightly 120.0a1(build ID: 20230928215127) on Windows 10, macOS 12, Ubuntu 22.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: