Open
Bug 1428578
Opened 8 years ago
Updated 3 years ago
crashed tab opened in background loses the URL
Categories
(Firefox :: Tabbed Browser, defect, P3)
Firefox
Tabbed Browser
Tracking
()
UNCONFIRMED
People
(Reporter: dietrich, Unassigned)
Details
(Keywords: regressionwindow-wanted, steps-wanted)
59.0a1 (2018-01-06) (64-bit) Mac OS X
STR:
1. Open some links in new tabs in background
2. Those background tabs crash
3. Go to those background tabs to try and reload and try again
Can't! The tab has the URL in the tab title, but the URL bar is blank!
We should make sure the URL makes it into the URL bar and persists, so the user doesn't lose it.
Comment 1•8 years ago
|
||
Is this a regression?
Flags: needinfo?(dietrich)
Keywords: regressionwindow-wanted
| Reporter | ||
Comment 2•8 years ago
|
||
I don't know. I haven't seen it anytime recently that I can remember.
Flags: needinfo?(dietrich)
Keywords: steps-wanted
Updated•8 years ago
|
Status: NEW → UNCONFIRMED
Ever confirmed: false
Priority: -- → P3
| Reporter | ||
Comment 3•8 years ago
|
||
I'm not sure why you've unconfirmed this. I've asked in #developers to see if there's a handy URL for crashing content processes, in order to allow you to see if this still happens.
Comment 4•8 years ago
|
||
(In reply to Dietrich Ayala (:dietrich) from comment #3)
> I'm not sure why you've unconfirmed this.
Because it may not be an issue anymore. If it is, somebody should confirm that.
> I've asked in #developers to see
> if there's a handy URL for crashing content processes, in order to allow you
> to see if this still happens.
I've had many content process crashes in the last few days -- bug 1431474. I haven't seen this bug happen, although it's possible I selected all tabs before they crashed.
Rather than waiting for a crash, it may also be possible to reproduce this by force-quitting a content process.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•