One more reminder that it's a lot friendlier to ask the user if they want to restore the session or not... because most of the time the current behavior is the opposite of what I want, and it's obnoxious to manually close a bunch of open tabs one at a time whenever I start the browser.
** Description changed: 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1369397 Title: [browser] can't make browser forget open pages Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Confirmed Status in webbrowser-app package in Ubuntu: New Bug 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. 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1369397/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
