Make autosave interval configurable

Please present your ticket in terms of functionality you are trying to achieve or problem this would address, particularly if it is based on experienced behavior with data. Closing as WONTFIX for now.

I think its absolutely ridiculous this was closed as wontfix, I see no reason or rhyme to why it should be that way from what you said.

Having said that, I can provide a real reason. It was previously requested and shot down to have autosave be a user configurable option, but shot down. A plugin can disable autosave easily via the script loader in 2.1, and the interval can be changed with filters via plugin as well.

WTF @ foolswisdom. I'm not new to this you know...

masquerade: valid points about the filters and now that I think of it, I can't really think of a widespread reason that one would want it off.

This did occur to me though: #3381

I stand by my comment. Present tickets in the problem or feature that they are to achieve, and then present possible solutions.

Err... he did?

Problem: Users cannot set autosave interval. Possible solution: Create option allowing users to set autosave interval.

What the christ is wrong with that?

Not being able to set something is not a problem in itself. Explaining the importance of why being able to set the interval is essential in this scenario.

Language like "ridiculous, WTF, and christ" hurts my feels, and I don't think is helpful.

In the same manner, Viper may think that you needlessly and senselessly closing a ticket without any real rationalization is rude and unhelpful, and will therefore respond in the same manner.

Replying to foolswisdom:

I stand by my comment. Present tickets in the problem or feature that they are to achieve, and then present possible solutions.

Well I'm glad you're the king of Trac. :rolleyes:

and I don't think is helpful.

Nor is closing tickets just because you think they are formatted improperly. Next time I'll write an essay for you.

Viper,

The issue is not one of formatting, but one of content. The reasoning of why an enhancement is important often reveals additional solutions.

I am sorry that the way I closed the ticket offended you, of course that was not my intention. I have deep respect for your fantastic contribution to WordPress.

Gmail functions well without this being configurable. Do you use Gmail, Viper007Bond? Is there a difference between Gmail's autosave and WP's autosave that makes you desire the interval to be configurable? Is it something we could fix?

I don't see the need for a configurable autosave interval. What problem exists at the moment because the interval is not configurable? What advantage is gained or what problem is solved if it is configurable?

I recommend closing as wontfix again, unless someone can come up with a reason why not being able to configure the autosave interval in any way detriments the user experience of writing and autosaving a post.

Changing milestone as 2.1 is out.