© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
(In reply to Mike Connor [:mconnor] from comment #189)
> six years down the
> road I don't see any compelling rationale for changing this behaviour for
> the majority of users.
1) It is six years down the road because no one has fixed this rather simple bug in all that time. The time the bug has gone unaddressed should not be used as a rationale to continue to not address it. On the contrary, that a simple bug has not been fixed in six years -- along with the number of people who want it fixed, as Sam points out in the previous comment -- should be motivation to prioritize fixing it.
2) The behavior needn't change for a majority of users, only those users who specifically desire the warning, and so indicate in their browser preferences.
> Setting it to true does not force a prompt, nor is
> that intended behaviour.
It is a change from behavior in older versions of Firefox. Where is this change in intent documented?
> The other cases seem like either
> corner cases we can decide on in isolation (i.e. better use of cache for
> restoring pages).
It seems a whole lot simpler to just pop up a warning if the user has indicated he wants one. I'm not sure why the fix that can be done in a couple of hours, honors what the user has asked for in his preferences, and will satisfy all the people who have voted for this bug, is seen as an inferior solution to the one that will take much longer to implement and not even solve the problem (you cannot guarantee that the user has set his cache to be large enough to hold everything in every tab that's open).