Closed Bug 1541930 Opened 5 years ago Closed 3 years ago

Restoring a session reverts to stale (or inconsistent) version of forms

Categories

(Firefox :: Session Restore, defect, P3)

66 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 706970

People

(Reporter: michael, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

  1. Ensure Firefox is configured to restore tabs from the previous session.
  2. Open an existing issue on Gitlab or Github in a new tab. (Other web sites might be suffering from similar issues, these are the two where I frequently come across this behavior.)
  3. Write a comment on the issue and submit.
  4. Ensure your comment has been added to the issue.
  5. Close Firefox.
  6. Restart Firefox.
  7. Examine the tab.

Optionally, after 3, switch to a different tab, and after 5, switch back to it (not sure if this is necessary).

Actual results:

My comment appears in the web form but not in the comment history of the issue itself. (Or it appears in both.)

Expected results:

Tab is restored as it was last viewed: comment appears in history, web form is blank.

I’ve been seeing this for quite a while with many different Firefox versions (so it is not a new bug), currently on 66.0.2 (64-bit) on Ubuntu 18.04.

Possibly related to #1270966 and/or #1316943.

Component: Untriaged → Session Restore

At this point - and with the information you provided - I can't yet tell if this is a bug specific to GitHub and/ or GitLab or in Firefox. I'm afraid I need more information, most importantly solid steps to reproduce (STR).

Priority: -- → P3

Since the code bases of these two services are not genetically related (at the most they might share some third-party components, or they might not), I would assume this to be a generic issue—at the very least with websites behaving in a certain way.

What other information would you need? Or how could I attempt to reproduce this in a manner that will enable you to work with it?

Alternatively, would you be able to set up a “playground” project on one of these two sites, try to reproduce the behavior and do further analysis from there?

This happens because a) the page isn't reloaded when a comment is submitted, and b) we load a cached version of the page when restoring. See bug 706970 for more discussion.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.