603098 - Improve the content process crash UX

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Mark Finkle (:mfinkle) (use needinfo?)]

Bug 594847 landed the basic functionality for a content process crash recovery system. This bug is about making the UX better. Some things to consider:

* Stop using a simple confirmation prompt and make a nicer error page. Should this be app modal or tab modal?
* Discuss the current system of reloading dead tabs, which uses Session Store and happens on tab selection (TabSelect event). Madhava originally proposed each dead tab would have an error page and would use the reload toolbar button to actually reload (See bug 594847 for more details)

Comment 1

[Madhava Enros [:madhava]]

This is what I'd suggested in the bug that preceded this one:


- when content crashes - we put up a message on the current tab, telling people
something happened and that they should reload (i.e. we don't auto-reload).
- set the other tabs so that they auto-reload when the user switches to them

This means that the user
- will see a message about what happened, and can make a decision (i.e. if the
current page is the problem, the user won't get into a reload cycle
- doesn't have to keep re-encountering the problem as he/she goes to other tabs
  - there's a bit of annoyance as those other pages reload, but it doesn't look
like we're continually running into a problem

and we're not reloading _everything_ all at once, which has its own problems.

We can use the diagonal-stripe style from the crashed plugin UI for the
background when we put up our message.  We should have the titlebar on screen
so that the reload button is accessible; the displayed title should be that for
the page that will reload when they hit reload (i.e. the "current" page).

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

If we get specific style changes we can open a new bug. This will also be changed based on the new Android dialog styling.