Open Bug 1576580 Opened 2 years ago Updated 1 year ago

Firefox session is restored in a new window after hard refresh

Categories

(Firefox :: Session Restore, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox-esr68 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- wontfix
firefox72 --- wontfix
firefox73 --- wontfix
firefox74 --- wontfix
firefox75 --- wontfix
firefox76 --- fix-optional

People

(Reporter: vlucaci, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

Affected versions

  • 69.0b16
  • 70.0a1 (2019-08-25)
  • 68.0.2

Affected platforms

  • Windows 10x64
  • macOS 10.14.6
  • Ubuntu 18.04x64

Steps to reproduce

  1. Launch FF.
  2. Access a few sites, perform several logins on various sites.
  3. Go to about:support.
  4. Click on the Refresh Firefox... button.
  5. A prompt message will be displayed, choose Refresh Firefox button.

Expected result

  • Once the hard refresh is complete, and the user chooses to restore the session(or only some tabs from session), all the tabs are loaded in the same window.

Actual result

  • Once the hard refresh is complete and the user chooses to restore the session(or only some tabs from session), all the tabs that are restored are opened in a new window, whilst the window from which the restore is made, is left in the background.

Regression range

  • Will return with regression ASAP.

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression
Has Regression Range: --- → no

I have managed to fiind a regression for this issue, here is the pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=42151fcd6cfc216d147730d0f2c6a2acd52d22fd&tochange=a0eb21bf55e1c1ae0ba311e6f2273da05c712799

QA Whiteboard: [qa-regression-triage]

I have manage to reproduce the issue on latest Nightly build 72.0a1 (2019-11-26).

Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.

This issue is reproducible on Firefox 73, 74 and 75 as well.

Hi Mike: Is it possible to get someone to look at this eventually and set a priority?

Flags: needinfo?(mdeboer)

Hi,

I was able to reproduce this issue on Ubuntu 18 with Firefox version Nightly 76.0a1 (2020-03-17) (64-bit). Marking that flag as affected.

The regression window in comment 2 doesn't contain a commit that looks like an obvious culprit to me :(
So I think this'll need some old-fashioned debugging and fixing.

Priority is low though and there's no sign of dataloss. Not sure if this is worth tracking; I think not.

Severity: normal → S4
Flags: needinfo?(mdeboer)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.