Restoring session after using RDM will lead to inconsistent state (URL bar != actual page)
Categories
(DevTools :: Responsive Design Mode, defect, P3)
Tracking
(firefox69 unaffected, firefox70 fix-optional)
Tracking | Status | |
---|---|---|
firefox69 | --- | unaffected |
firefox70 | --- | fix-optional |
People
(Reporter: beth, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression, Whiteboard: [rdm-reserve])
STR:
- Go to example.com
- Enter RDM
- Navigate to another page (e.g., google.com)
- Leave RDM
- Force-close the browser
- Start the browser
- Restore session
ER:
The URL bar should contain the correct URL, not example.com
AR:
You will be at the second page (google.com in this example) but the URL bar will contain example.com
Reporter | ||
Comment 1•5 years ago
•
|
||
After further investigation, on beta the wrong page will be restored (e.g., example.com) but the URLbar will contain the matching URL (example.com). This is really only an issue on Nightly.
Reporter | ||
Comment 2•5 years ago
|
||
Upon further further investigation, this is not because of bug 1510569. (I had just assumed it was because this seemed similar to the other RDM bug (bug 1562821)).
:alchen, you've been working on session restore lately. Have you seen this? Do you know if this is because of your work?
Comment 3•5 years ago
|
||
I will be off until next Thursday.
From comment 1, it is an issue happened on Nightly.
Request a regression-window-wanted first.
Comment 4•5 years ago
|
||
This is the regression window I got - https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=50fec259d5a66e44a087253fa5f9f805d32e8ef3&tochange=ad05396bfeed949a112401d661c5d943f775f761
Note that sometimes after the Step 4 (Leave RDM) in STR in comment 0 , I saw the URL became "example.com" while I stayed at the google.com page, even without force-quit and restore.
Reporter | ||
Comment 5•5 years ago
|
||
:hsinyi, the patch for bug 1562821 fixes that issue but not the session restore bit.
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Can you mark up which branches are affected here? Is it just 70, and if so, any chance we'll fix this in 70 as well?
Reporter | ||
Comment 8•5 years ago
|
||
This only affects 70.
Updated•5 years ago
|
Comment 9•5 years ago
|
||
Happy to take a patch for 70 but marking fix-optional to remove this from our weekly triage.
Updated•2 years ago
|
Description
•