Implement crash dialog as an infobar
Bug #936491 reported by
Danielle Foré
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Midori Web Browser |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
I noticed this morning that Chromium displays a little message about crashes just like Midori does. But their implementation is a bit smarter than ours: they use an infobar. Why is this smarter?
It's more compact. It's one less window to deal with. It's not in my way. It's there when you want it, but it's easy to ignore if you don't.
I'd love to see our crash dialog replaced with a much more concise infobar.
| Changed in midori: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
This is not purely about choosing the UI. The dialog allows you to change preferences, disable extensions and choose not to open your session. The browser may already be crashing while trying to show the infobar.
I do like the idea as far as allowing the user to not load the session. The problem is that we don't easily know what caused the crash. Chromium evidently has the advantage that the browser window is immune to crashes beyond GLib/ GTK+ itself.
Realistically we need to wait for WebKit2.