After loading restored tab, firefox navigates to new URL
Categories
(Firefox :: Session Restore, defect, P3)
Tracking
()
People
(Reporter: mgaudet, Unassigned, NeedInfo)
References
(Blocks 2 open bugs)
Details
(Keywords: dataloss, regressionwindow-wanted, steps-wanted, Whiteboard: QA-not-reproducible)
I just quit Firefox to change a setting (disabling web-render, but I've seen this on random session restores a few times).
I had three tabs open:
- Gmail
- A blog post
- about:config
When I restarted, the three tabs were what I expected, and about:config loaded again. Cool.
Then I switched back to tab 2, which had the blog post i was reading. The tab text had the right info on it, but when I switched to the tab firefox navigated to an old URL that I think was in that tab earlier.
Then, while writing this bug report I bothered to load the gmail tab: Same thing happened. Sudden navigation.
I say navigation because in both instances the expected tab shows up in the back button history as the previous page, and hitting back takes me back to the expected page.
This has happened intermittently on restart for nightly update for a while.
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:mikedeboer, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 2•4 years ago
|
||
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.)
Comment 3•4 years ago
|
||
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.)
Comment 4•4 years ago
|
||
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.)
Comment 5•4 years ago
|
||
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 --
.
Updated•4 years ago
|
Similar situation is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1522184
The only difference is the way the tab was made not active (by browser restart in this bug - Bug 1624083, or by discard extension - in Bug 1522184).
Comment 7•4 years ago
|
||
I have attempted reproducing this issue by repeating the steps described in comment 0 on a Windows 10 machine and a Nightly v79.0a1 browser.
I had no success reproducing it in any different situations I could think of.
Has this issue occurred again in the meantime? Do you have any new suspicions of the real cause of this issue?
Which operating system and browser version were you using when it reproduced? Thanks!
Comment 9•4 years ago
|
||
Adding the QA Whiteboard [qa-regression-triage], but please remove it it if new info is available for QA to reproduce it.
Comment 10•4 years ago
|
||
(In reply to Bodea Daniel [:danibodea] from comment #7)
… no success reproducing it …
(In reply to Matthew Gaudet (he/him) [:mgaudet] from comment #0)
… random …
… intermittently …
Gut feeling: think about whether – prior to quit – any open tab had been at any time in a discarded state.
Consider the equivalence (and sychronisation) of the three values mentioned in bug 1498432 comment 5. Probably not directly related, but maybe food for thought.
Comment 11•2 years ago
|
||
After re-attempting to reproduce the issue in bug 1624083 and bug 1522184, as those were reported as very similar, but wasn't able to confirm any of them by using the steps in the bug descriptions in both their originally reported versions as affected and the latest versions of Nightly.
I have attempted to discard the tabs before the restart or quitting action, however, I wasn't able to observe the reproduction of any suspicious behavior.
Also considering that the reporter has not observed the issue, later on, pet comment 8, I will set the whiteboard "QA-not-reproducible".
In case this issue reoccurs and further information is provided, please NI me to re-attempt reinvestigation of a regressor.
Comment 12•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 10 votes.
:dao, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Description
•