Revision history [back]

Use-case: I'm writing a mail, I do a sloppy motion that's interpreted by Sailfish as a left-to-right ("back") swipe, which really wasn't what I wanted to do.

This unceremoniously discards my message. Not nice; in fact I'm considering this a bug; a device should never drop user data without warning, IMHO.

I see three options:

1. Either somehow intercept that swipe and get the user to either: a) confirm the discard, b) save to drafts, c) continue working on the message

2. Or automatically save the message in a Drafts folder

3. Or a remorse timer. If the user clicks it, go back to the compose view

Use-case: I'm writing a mail, I do a sloppy motion that's interpreted by Sailfish as a left-to-right ("back") swipe, which really wasn't what I wanted to do.

This unceremoniously discards my message. Not nice; in fact I'm considering this a bug; a device should never drop user data without warning, IMHO.

I see three options:

1. Either somehow intercept that swipe and get the user to either: a) confirm the discard, b) save to drafts, c) continue working on the message

2. Or automatically save the message in a Drafts folder

3. Or a remorse timer. If the user clicks it, go back to the compose view

Use-case: I'm writing a mail, I do a sloppy motion that's interpreted by Sailfish as a left-to-right ("back") swipe, which really wasn't what I wanted to do.

This unceremoniously discards my message. Not nice; in fact I'm considering this a bug; a device should never drop user data without warning, IMHO.

I see three options:

1. Either somehow intercept that swipe and get the user to either: a) confirm the discard, b) save to drafts, c) continue working on the message

2. Or automatically save the message in a Drafts folder

3. Or a remorse timer. If the user clicks it, go back to the compose view