Open Bug 1312198 Opened 8 years ago Updated 2 years ago

[e10s] Crashed tab UI is misleading by only indicating a single crashed tab

Categories

(Firefox :: Tabbed Browser, defect)

defect

Tracking

()

People

(Reporter: aleth, Unassigned)

References

Details

When a tab crashes, a red exclamation mark appears in the tab favicon. But because there is currently still only a single (or small number of) content process, all the other tabs in the same process are affected as well. This should also be indicated by a suitable favicon change.

If this is not done, the crashed tab information text is misleading because the user may think that the other tabs are not affected and erroneously choose "restore only this tab" as a consequence.
Flags: needinfo?(mconley)
In the single content process case, when the content process crashes, we only show about:tabcrashed for the selected browser, and put the rest of the tabs in the "pending state", which causes the tabs to reload upon click.

I agree that the text is misleading. We're working on better text as a consequence of bug 1309316.
Depends on: 1309316
Flags: needinfo?(mconley)
(In reply to Mike Conley (:mconley) - (digging out of review / needinfo backlog) from comment #1)
> I agree that the text is misleading. We're working on better text as a
> consequence of bug 1309316.

Part of the problem is that the selected browser shows the crash tab page, but it's all "this tab" language. There's no indication that there may be data/state loss in all the other tabs as well.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.