all commands subject to busy?

[ldeviator]

in app.css, all commands including compose, reply, reply-all, forward, delete and print will not fire if the interface is locked (set to busy)

I think that compose certainly should not be subject to busy since it loads a new page and doesn't have any bearing on the currently displayed message.

Additionally reply, reply-all, forward, delete and print work on the appropriate message in my testing even when the message is not fully loaded.

Waiting for a message to load before you can reply to it, just to have the message load again after a new page load is slower than it needs to be. Same with print.

Delete may be a bit of a problem, but so far it works for me.

Applying this patch makes the interface snappier when someones wants to do these functions and the interface is set to busy from either checking mail or loading a message.

[ldeviator]

remove busy restrictions on compose, reply, reply-all, forward, delete, and print

[alec]

We have race-conditions problem in session, so enabling compose, reply, forward actions will disallow to upload attachments. There should be no problems with print, delete and maybe some other actions, but we should also add task=mail condition.

[alec]

It's possible to delete/print message without loading it first. This ticket/patch is outdated, so I'm closing it.