Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Session Restore causes javascript bug

  • 1 reply
  • 1 has this problem
  • 6 views
  • Last reply by guigs

andreamconnell
andreamconnell
more options

Full details at http://stackoverflow.com/questions/28997027/firefox-session-restore-causes-bug-in-javascript

I have written a web application in which users have found a problem after Firefox session restore. If the user has a record open when FIrefox crashes, that record will open again when the browser is restored. However, a split second after opening many of the fields on the record will be overwritten with data from the last form they had *submitted* before the crash.

So the scenario is that the user opens record A, edits, and saves (submitting the form). They then open record B. Before they have saved, Firefox crashes. When they restart Firefox, they see record B for a split second, and then the data is replaced with data from record A.

I can reproduce this problem and have confirmed that the data is being populated from the recovery.js file in my profile directory (sessionstore-backups).

Any ideas what is going on here or how I can prevent this from happening without asking all users to turn off Firefox's session restore feature?

Full details at http://stackoverflow.com/questions/28997027/firefox-session-restore-causes-bug-in-javascript I have written a web application in which users have found a problem after Firefox session restore. If the user has a record open when FIrefox crashes, that record will open again when the browser is restored. However, a split second after opening many of the fields on the record will be overwritten with data from the last form they had *submitted* before the crash. So the scenario is that the user opens record A, edits, and saves (submitting the form). They then open record B. Before they have saved, Firefox crashes. When they restart Firefox, they see record B for a split second, and then the data is replaced with data from record A. I can reproduce this problem and have confirmed that the data is being populated from the recovery.js file in my profile directory (sessionstore-backups). Any ideas what is going on here or how I can prevent this from happening without asking all users to turn off Firefox's session restore feature?

All Replies (1)

guigs
guigs
more options

Do you have the crash report handy?

To set the right expectations, this forum is for basic troubleshooting, if development forums cannot answer this question, more details might be needed about the application.

If you are sure it is an issue in Firefox, go to Bugzilla.mozilla.com with a public url, steps to reproduce and crash report from a clean Firefox profile might be required for investigation.