© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
(In reply to :Gavin Sharp (email <email address hidden>) from comment #193)
> (In reply to Sam Steingold from comment #191)
> We do not draw conclusions solely based on volume of Bugzilla activity, and
> we certainly don't extrapolate that feedback across our entire user base
> blindly.
Nobody said that you should. This kind of rhetoric isn't very helpful.
> > C-q should be protected by a warning. No other major browser - Opera or
> > Chrome - has the obnoxious behavior of dying on a typo (wiping the sessions
> > and downloads).
>
> As mentioned already in this bug, we do not "wipe sessions and downloads" on
> Cmd+Q.
Nonetheless there's a plethora of cases that will cause data loss.
> I'm not claiming there are no problems with our existing behavior worth
> addressing, just that this bug is no longer a useful place to track them.
> There are other bugs that already cover related issues (bug 667912, bug
> 565567, bug 404081, bug 628156), and I encourage people to file new,
> narrowly focused bugs if they have specific suggestions/issues not already
> covered.
"Implement hold threshold timer"? Very discoverable. Yeah I see this very much being implemented :-/
What to say about bug 565567? It could be rephrased "implement bug 419009 but only on Mac"! Now you're getting cute. (At least the ticket contains a link to a seemingly helpful extension: https:/
The other two aren't quite the same issue as this.
> At a very high level, I do not think we will be changing the "avoid
> prompting and make it easy to restore" stance.
I can't see how it is a win not to ask in a situation you'll lose either private windows, non-resuming downloads, modified inputs on "Web 2.0" pages or poorly-made old-style pages, etc.