726525 - Firefox doesn't correctly load an already opened website when updating to a new version

Status: RESOLVED INCOMPLETE

(Firefox :: Session Restore, defect)

Description

[Mihai Maerean]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
Build ID: 20120208060813

Steps to reproduce:

I was visiting http://redgoblin.ro/shop/?lang=en using Firefox 10 when Firefox prompted me that 10.0.1 is available so I went ahead and installed it.
After the installation, Firefox tried to display the web pages that were open before the installation but it failed to correctly open this website.
I tried to duplicate the problem by terminating the firefox.exe process from Task Manager but the problem seems to happen only when updating Firefox.

I am the one who created the Red Goblin web site (back in 2008) and I am seeing these JavaScript exceptions (sent back through AJAX) for a few Firefox users. Today, I finally managed to reproduce it.

The website is built as an web application so the user stays on a single web page for the entire duration of the visit.
There are some elements that are loaded through AJAX, but there's a big chunk of data that is needed from the server and the website gets it by sending a POST request in an IFRAME. The IFRAME then sends the data to the page on the ONLOAD event.

When loading the page after upgrading Firefox, the browser doesn't perform the POST request for the IFRAME like it normally does.


Actual results:

the website should have been loaded like it normally does when visiting the website in Firefox


Expected results:

After upgrading, Firefox should load the already opened websites using the usual loading sequence and not skip some of the steps in loading them.

Comment 1

[[:Aleksej]]

bug 423800?

Comment 2

[Wayne Mery (:wsmwk)]

(In reply to [:Aleksej] from comment #1)
> bug 423800?

Mihai, what do you think?

Comment 3

[Firefox Bug Husbandry Bot]

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.