canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627
edits
Complete Send In Background: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
|Feature stage=On hold | |Feature stage=On hold | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note=up for grabs | |Feature status note=up for grabs | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 11: | Line 11: | ||
|Feature overview=Send in Background is intended to remove the interrupt of the user between clicking on send and having a visual sudo-block to be able to continue using and processing email. | |Feature overview=Send in Background is intended to remove the interrupt of the user between clicking on send and having a visual sudo-block to be able to continue using and processing email. | ||
|Feature users and use cases=When a user hits send, we currently display a progress dialog whilst the send is in progress and the file is saved to the sent folder. | |Feature users and use cases=When a user hits send, we currently display a progress dialog whilst the send is in progress and the file is saved to the sent folder. | ||
| Line 17: | Line 17: | ||
This allows the user to continue working with email, whilst still sending the email. | This allows the user to continue working with email, whilst still sending the email. | ||
If there is an error whilst sending the email, then Thunderbird can decide what to do, whether to try again later, or notify the user, or a mixture of both. | |||
One area we have to be careful with is shutdown - if Thunderbird is in the process of sending an email, we shouldn't abort that - but allow it to be finished (whilst also informing the user). Additionally, if emails are waiting to be sent, we should potentially alert about those as well. | |||
|Feature implementation plan={{Bug|511079}} is the tracking bug. | |||
|Feature qa review=[[Thunderbird/TestPlans/SendInBackground]] | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||