Open Bug 1830233 Opened 1 year ago Updated 10 months ago

Newly created Profiles/ Data are not displayed in the new migration window if created while Firefox is running until Firefox is restarted

Categories

(Firefox :: Migration, defect, P3)

Firefox 114
Desktop
All
defect

Tracking

()

Tracking Status
firefox-esr102 --- unaffected
firefox112 --- unaffected
firefox113 --- unaffected
firefox114 --- wontfix
firefox115 --- wontfix

People

(Reporter: atrif, Unassigned)

References

(Blocks 2 open bugs, Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Found in

  • 114.0a1 (2023-04-26)

Affected versions

  • 114.0a1 (2023-04-26)
  • 113.0b8 (disabled)

Tested platforms

  • Affected platforms: macOS 12, Windows 10x64, Ubuntu 20.04
  • Unaffected platforms: none

Preconditions

  • browser.migrate.content-modal.enabled:true

Steps to reproduce

  1. Open Firefox and Chrome
  2. Create a new profile in Chrome and add at least one bookmark.
  3. Open the migration window and search for the created profile at step 3.

Expected result

  • The profile is displayed.

Actual result

  • The newly created profile is not displayed.

Regression range

  • Most likely started with the implementation of the new Import Wizard Experience. I will search for one ASAP if there is one. The newly created profile is displayed on the old Import Wizard experience.

Additional notes

  • Attached a screen recording.
  • The issue does not reproduce after a Firefox restart.
  • This only happens if Firefox is opened when a new profile or new data is added in the browsers we are migrating from.
  • Sometimes new profiles appear so the issue may be intermittent.
Priority: -- → P3
QA Whiteboard: [qa-regression-triage]

It seems that this started with bug 1821744. I even tried Firefox 112.0a1 (2023-03-05) with browser.migrate.content-modal.enabled:true and this is still reproducible. I am setting bug 1821744 as the regressor.

Regressed by: 1821744

:mconley, since you are the author of the regressor, bug 1821744, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(mconley)

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

Blocks: 1801313
No longer blocks: 1821736
Flags: needinfo?(mconley)

:mconley is the priority/severity still accurate now that the pref is no longer limited to Nightly and impacts Fx115?

Flags: needinfo?(mconley)

Yes, I'd still stand by that priority / severity. I suspect the majority of users that are migrating data or doing so on older profiles on other browsers, and not profiles that were created while Firefox was open.

Flags: needinfo?(mconley)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: