On long loading pages that eventually give a 502 error (like b.m.o sometimes is) the loading throbber in background tabs get a "hourglass" icon. Then on session-restore, those tabs have blank tab-titles
Categories
(Firefox :: Session Restore, defect, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: dataloss)
Attachments
(5 files)
1.You need a website with very slow response (Like b.m.o sometimes get these days) where it will take a loooooong time to load, and sometimes even throw a 502 errror
2. try to open a tab like this
3. Put that tab in the background
4. Wait
5. After some time, the loading throbber of the tab becomes a "hourgalss" - See attached screenshot.
6. Now close firefox and reopen. Use History->Restore previous session
7. The "hourglass" tab from Step 5 will have a blank tab-title
AR:
- The throbber becomes a static "hourglass" icon
- On session restore, the tabs with the hourglass icon have an empty/blank tab-title.
| Reporter | ||
Comment 1•1 year ago
|
||
| Reporter | ||
Comment 2•1 year ago
|
||
| Reporter | ||
Comment 3•1 year ago
•
|
||
From bug 1812019, i am guessing that the hourglass is the intended behaviour?
But is the blank tab-title on session restore also by design?
Edit: The two issues I described may actually be separate issues, i just filed the bug as I understood it.
| Reporter | ||
Comment 4•1 year ago
|
||
| Reporter | ||
Comment 5•1 year ago
|
||
Comment 6•1 year ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 7•1 year ago
|
||
The severity field is not set for this bug.
:sfoster, could you have a look please?
For more information, please visit BugBot documentation.
Comment 8•1 year ago
|
||
There may be a bug on file for this already, but I wasn't able to find it. Essentially we should considering recording the URL of the tab in the session, even if we've not yet got a response from it before the browser quits and the session gets written. I've seen this cause data-loss if you restore a session in the browser without a stable network connection (say on a train), then when you restart again at home you find all those tabs got replaced with about:blank.
Updated•1 year ago
|
Updated•1 year ago
|
| Reporter | ||
Comment 10•8 months ago
|
||
I havent seen this in a long time. Will close this as WFM.
Description
•