https://bugzilla.wikimedia.org/show_bug.cgi?id=17064
Brion Vibber <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Brion Vibber <[email protected]> 2009-01-20 03:39:03 UTC --- I would certainly appreciate having my typographical edits not be lost if my browser crashed, just as much as I would appreciate not losing any other edit. Redoing stuff is annoying! I can see no reason to allow disabling drafts outright. Its UI is minimal, and the benefit of being able to recover data far outweighs the hypothetical benefit of hiding a button. Making the autosave frequency configurable could be done, but honestly I don't see a big use case for it. If you leave the page open without editing, no data gets transferred. Automatic saves after a change are in the background and should not interfere with the UI. Being text, it should generally be pretty fast. If you're on a very slow connection with a very large article open, perhaps it might be slightly annoying... but it's still not likely to cause much trouble I can think of -- it'll generally be doing its business while you're typing, not while you're fiddling with some other page. Can you provide an example case where the automatic save is disruptive, and some details of *how* it's disruptive? What are some strategies that could tackle that, such as changing the autosave rate or transferring smaller amounts of data? -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
