| 2014-09-15 04:53:35 |
Selene ToyKeeper |
bug |
|
|
added bug |
| 2014-09-15 09:25:06 |
David Barth |
webbrowser-app: status |
New |
Confirmed |
|
| 2014-09-15 09:25:11 |
David Barth |
webbrowser-app: importance |
Undecided |
High |
|
| 2014-09-15 09:25:23 |
David Barth |
tags |
rtm14 ueqa |
rtm14 touch-2014-09-18 ueqa usability |
|
| 2014-09-15 09:26:18 |
David Barth |
webbrowser-app: assignee |
|
Alexandre Abreu (abreu-alexandre) |
|
| 2014-09-15 13:50:30 |
Alexandre Abreu |
marked as duplicate |
|
1362543 |
|
| 2014-09-19 15:04:17 |
Bill Filler |
removed duplicate marker |
1362543 |
|
|
| 2014-09-19 15:04:32 |
Bill Filler |
tags |
rtm14 touch-2014-09-18 ueqa usability |
rtm14 touch-2014-09-25 ueqa usability |
|
| 2014-09-24 14:33:40 |
Olivier Tilloy |
webbrowser-app: assignee |
Alexandre Abreu (abreu-alexandre) |
|
|
| 2014-09-24 14:51:26 |
Bill Filler |
tags |
rtm14 touch-2014-09-25 ueqa usability |
rtm14 ueqa usability |
|
| 2014-09-24 14:52:16 |
Bill Filler |
tags |
rtm14 ueqa usability |
ueqa usability |
|
| 2014-09-24 14:52:26 |
Bill Filler |
bug task added |
|
ubuntu-ux |
|
| 2014-09-26 16:28:09 |
Olga Kemmet |
summary |
can't make browser forget open pages |
[browser] can't make browser forget open pages |
|
| 2014-09-26 16:29:37 |
Olga Kemmet |
ubuntu-ux: assignee |
|
Giorgio Venturi (giorgio-venturi) |
|
| 2014-09-29 14:39:39 |
Giorgio Venturi |
description |
After killing the browser app, each subsequent restart will open it with the same set of pages open. In theory this might be a nice feature, but it's kind of a problem if one of those pages causes the browser to crash or lock up. The browser app then becomes unusable without manually removing its config.
Could we make it ask on launch whether to re-open previous pages, and let the user choose to start fresh if desired?
I've noticed this a lot lately, but the specific version I'm using now is from rtm krillin image 33. |
After killing the browser app, each subsequent restart will open it with the same set of pages open. In theory this might be a nice feature, but it's kind of a problem if one of those pages causes the browser to crash or lock up. The browser app then becomes unusable without manually removing its config.
Could we make it ask on launch whether to re-open previous pages, and let the user choose to start fresh if desired?
I've noticed this a lot lately, but the specific version I'm using now is from rtm krillin image 33.
-- SOLUTION --
1) If a crash happens, the browser will have an error page on restart, rather than the page the caused the crash.
2) If user wants, he will be able to reload the page (and potentially crash the browser again).
3) All the other tabs should persist. |
|
| 2014-09-29 14:39:44 |
Giorgio Venturi |
ubuntu-ux: status |
New |
In Progress |
|
| 2014-10-02 13:34:10 |
Giorgio Venturi |
ubuntu-ux: importance |
Undecided |
Medium |
|
| 2014-10-02 13:40:03 |
Giorgio Venturi |
description |
After killing the browser app, each subsequent restart will open it with the same set of pages open. In theory this might be a nice feature, but it's kind of a problem if one of those pages causes the browser to crash or lock up. The browser app then becomes unusable without manually removing its config.
Could we make it ask on launch whether to re-open previous pages, and let the user choose to start fresh if desired?
I've noticed this a lot lately, but the specific version I'm using now is from rtm krillin image 33.
-- SOLUTION --
1) If a crash happens, the browser will have an error page on restart, rather than the page the caused the crash.
2) If user wants, he will be able to reload the page (and potentially crash the browser again).
3) All the other tabs should persist. |
After killing the browser app, each subsequent restart will open it with the same set of pages open. In theory this might be a nice feature, but it's kind of a problem if one of those pages causes the browser to crash or lock up. The browser app then becomes unusable without manually removing its config.
Could we make it ask on launch whether to re-open previous pages, and let the user choose to start fresh if desired?
I've noticed this a lot lately, but the specific version I'm using now is from rtm krillin image 33.
-- SOLUTION --
1) If a crash happens, the browser will have an error page on restart, rather than the page the caused the crash.
2) If user wants, he will be able to reload the page (and potentially crash the browser again).
Design here:
https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3c37ea932_70
Note: All the other tabs should persist. |
|
| 2014-10-02 13:40:08 |
Giorgio Venturi |
ubuntu-ux: status |
In Progress |
Fix Committed |
|
| 2014-10-21 17:40:01 |
Olivier Tilloy |
webbrowser-app: importance |
High |
Medium |
|
| 2014-10-21 17:41:28 |
Olivier Tilloy |
tags |
ueqa usability |
design-gap ueqa usability |
|
| 2014-12-01 21:00:54 |
Selene ToyKeeper |
description |
After killing the browser app, each subsequent restart will open it with the same set of pages open. In theory this might be a nice feature, but it's kind of a problem if one of those pages causes the browser to crash or lock up. The browser app then becomes unusable without manually removing its config.
Could we make it ask on launch whether to re-open previous pages, and let the user choose to start fresh if desired?
I've noticed this a lot lately, but the specific version I'm using now is from rtm krillin image 33.
-- SOLUTION --
1) If a crash happens, the browser will have an error page on restart, rather than the page the caused the crash.
2) If user wants, he will be able to reload the page (and potentially crash the browser again).
Design here:
https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3c37ea932_70
Note: All the other tabs should persist. |
After killing the browser app, each subsequent restart will open it with the same set of pages open. In theory this might be a nice feature, but it's kind of a problem if one of those pages causes the browser to crash or lock up. The browser app then becomes unusable without manually removing its config.
Could we make it ask on launch whether to re-open previous pages, and let the user choose to start fresh if desired?
I've noticed this a lot lately, but the specific version I'm using now is from rtm krillin image 33.
-- SOLUTION --
1) If a crash happens, the browser will have an error page on restart, rather than the page the caused the crash.
2) If user wants, he will be able to reload the page (and potentially crash the browser again).
Design here:
https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3c37ea932_70
Note: All the other tabs should persist.
Note: The above solution does not address the common use case of "I want a fresh, empty browser instance", or "I want to choose whether to restore my session", which is what many people seem to want. |
|
| 2014-12-01 21:11:12 |
Launchpad Janitor |
webbrowser-app (Ubuntu): status |
New |
Confirmed |
|
| 2015-01-05 16:18:36 |
Michał Sawicz |
bug |
|
|
added subscriber Michał Sawicz |
| 2015-04-14 18:03:47 |
Olivier Tilloy |
webbrowser-app: status |
Confirmed |
Fix Released |
|
| 2015-04-14 18:03:53 |
Olivier Tilloy |
webbrowser-app (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2015-05-08 13:48:55 |
James Mulholland |
ubuntu-ux: assignee |
Giorgio Venturi (giorgio-venturi) |
James Mulholland (jamesjosephmulholland) |
|
| 2015-05-08 14:45:35 |
James Mulholland |
ubuntu-ux: status |
Fix Committed |
Fix Released |
|
