1750468 - HTTP-EQUIV="REFRESH" is creating multiple history entries

Status: RESOLVED DUPLICATE of bug 1742865

(Core :: DOM: Navigation, defect)

Description

[Johnny Klonaris]

Attachment: IMG_6588_2.png

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

Steps to reproduce:

Our QA system wraps log files with a simple html file. The file has:
<meta HTTP-EQUIV="REFRESH" content="300">
and includes the file with something like:
<!--#include virtual="create_gCloud_host.Squirrel.2022.01.16-071620.log" -->
Which allows us to browse through logs with a web browser.

Actual results:

Each time the page reloads, it appears to create a new history entry. Clicking the back arrow no longer returns to the previous page, but instead there are dozens or even hundreds of links to the current page, all identical.

Expected results:

Until recently, hitting the back arrow would return to the parent page - basically a link to the log page and related information.

Now, esp. if I leave the page overnight - which is reasonable as some of these tasks can take a day or more - I have to click back through dozens/hundreds of links - or find the log by starting over.

This used to work as expected: the back arrow goes to the previous page - I believe it was a month or two ago that this started.

Please either change this back or provide an option to revert this behavior.

Thank you.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Navigation' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Masatoshi Kimura [:emk]]

I could not reproduce the issue. Could you attach a minimal testcase?

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

Peterv, didn't you fix something related to this recently. I'm thinking bug 1742865.

Comment 4

[Johnny Klonaris]

Yes - this absolutely looks like bug 1742865. My Firefox just this morning updated to 96 - it looks like the fix to bug 1742865 is or will likely be in 97.

I'll keep my eyes open.

Comment 5

[Johnny Klonaris]

This is too funny, After seeing the comments above I realized I should create something that could show the problem. Eventually I came up with this: http://jawknee.com/reload.html

At first it was just a page reloading, but it didn't show the problem. I had to get back to work, but I thought that maybe the SSI was involved Tried this and that and page would load, and reload - but no sign of the problem. So I checked a tab pointed at one of the work pages that had shown the problem and IT didn't have the problem. That's when I remembered that just after I had posted to the bug, Firefox suggested it was time for an update and I took it. That brought me from 95 to 96, but I didn't pay it much mind because it seemed like the problem might fixed in 97.

So I checked on my laptop and it was on 95, and it DID show the problem.

So pretty much looks to be fixed in 96!!