User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

Note: Have not been able to intentionally reproduce this, but it has happened repeatedly.

1. Use a tab, visit multiple pages / Click through links
2. Close tab (I sometimes use CMD+W and sometimes use the x button, in case that impacts it. Not sure which I've used when encountering this bug)
3. Reopen tab

Actual results:

Reopened tab does not show the page that was closed, but shows a previous page accessed by the tab. Previous pages can be accessed with "Go back one page" but I cannot "Go forward" to the page that was accessed last and closed.

Expected results:

The tab should reopen as it was when closed, with the most recent page that it accessed.

Hi Tobey,

I wasn't able to reproduce this issue on Firefox 75 or Firefox 77.0a1 on MacOS 10.15 or Windows 10

Did this issue only occur recently or it happened on earlier versions before as well?
Since you aren't able to reproduce this intentionally either, could you check if it occurs on the latest Firefox versions within the next few days?
If it does, maybe try to write down how it happened exactly?

Thank you!

Is happening also to me, and I think https://bugzilla.mozilla.org/show_bug.cgi?id=1624083 is the same problem. It has been happening since some update, and it surprises me to find too few bugs about it or comments about it.

I'm on firefox 75.0 on windows 10. I can reproduce it intentionally. For example:
Step 1. Enter to https://about.gitlab.com/blog/2020/03/30/new-features-to-core/
Step 2. Navigate, in my case I went to Support, and then to Pricing.
Step 3. Close the tab, I used Ctrl + W, but I suppose it doesn't matter.
Step 4. Press Ctrl + Shift + T to reopen the tab.

Actual results:
I'm again in https://about.gitlab.com/blog/2020/03/30/new-features-to-core/ instead on Pricing that was the last page that I visited.

(In reply to set.tobur from comment #2)

Is happening also to me, and I think https://bugzilla.mozilla.org/show_bug.cgi?id=1624083 is the same problem. It has been happening since some update, and it surprises me to find too few bugs about it or comments about it.

I'm on firefox 75.0 on windows 10. I can reproduce it intentionally. For example:
Step 1. Enter to https://about.gitlab.com/blog/2020/03/30/new-features-to-core/
Step 2. Navigate, in my case I went to Support, and then to Pricing.
Step 3. Close the tab, I used Ctrl + W, but I suppose it doesn't matter.
Step 4. Press Ctrl + Shift + T to reopen the tab.

Actual results:
I'm again in https://about.gitlab.com/blog/2020/03/30/new-features-to-core/ instead on Pricing that was the last page that I visited.

I was doing some research, I tried to go to about:profiles and restart firefox without extensions, and I didn't have the bug, after some tests I saw that the extension causing the problem was Nellitab which is an extension that modifies the normal behavior of new tab. So my hypothesis is that when we reopen the tab firefox now is calling new tab, nellitab and other extensions are messing with the call and returning a previous page than the last one.

Seems that this bug is from even before Quantum https://www.reddit.com/r/firefox/comments/5zyrea/undo_close_tab_bugged/. And another one that is how I got here https://www.reddit.com/r/firefox/comments/fzj38e/firefox_doesnt_reopen_tabs_properly/

I created 3 gifs to show the problem, in the first one I show the normal behavior, and in the other 2 I tried with different addons that change the new tab https://imgur.com/a/L1f9JQr

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.)

Hello,

I have managed to reproduce the issue based on the STR from Comment 2 with multiple add-ons that override New Tabs (Tabliss, NelliTab and New Tab Override) on Release 75.0 and Release 76.0.1 under Windows 10 Pro 64-bit. The latest Beta and Nightly seem to not be affected by the issue.

I have performed a regression range on the issue and narrowed it down to https://bugzilla.mozilla.org/show_bug.cgi?id=1601779 (2020-05-20T12:53:05.233000: DEBUG : Found commit message: Bug 1601779 - Try using response process selection more often for front-end loads. r=kmag) with this differential revision https://phabricator.services.mozilla.com/D58890.

This is the corresponding pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=325da10270e4bbc644df0fd29a6c3f6ef536d262&tochange=a9b06feb5942c5e16bcf9adefe84e081edc402c7 .

Hi alex, can you bisect the fix range on this one?

Hello Tim,

I bisected the fix range as requested and narrowed it to the following https://bugzilla.mozilla.org/show_bug.cgi?id=1627420 (2020-05-28T10:14:29.757000: DEBUG : Found commit message: Bug 1627420 - Ensure we clear userTyped properties when doing a process flip. r=mattwoodrow) with the following differential revision https://phabricator.services.mozilla.com/D69862.

This is the corresponding pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b7d4ff29805ddabfebebb34b1e5beee07fcad45b&tochange=cabf2a947f7e5b8a04965df9f0ca5146e82dfd1c .

I hope this is correct. In case of any error on my part, please let me know and I’ll bisect once more. Thank you !

Matt, either regression seems to be patches from you, but I suspect the one in comment 10.