[tim_iles]

In Messaging on the Facebook app on Android, you have Send on the left and Clear on the right. Gets me far too often, and it's just not even necessary. If I don't want to send what I started writing, I simply hit back. Hate it.

[pbhjpbhj]

What in the interface tells you that navigating away from the page will not submit the data?

Perhaps instead of reset a "do not submit" button is required. But then if I changed my mind about what I'm writing but still want to send a message things get a little lame.

How can you tell for example that going back doesn't instead save the comment as a draft (like the SMS interface on my [pretty old] Sony Ericcson phone).

I disagree with the article, I think there is a place for a reset/clear function.

[tim_iles]

The expected behaviour is that navigating away will not submit the data. That's pretty much consistent across all interfaces I know, with the exception of saving as draft, which still does not "submit" the data to the human recipient on the other end.

However, I do agree that clearing the message can have its uses, but as it's a secondary action, it deserves a far less prominent position for the button (e.g. maybe as an option on the long-touch menu, but at least not where you'd expect the Send button to be). On this app, it's in the primary action space and doesn't ask confirmation before wiping your message.

[f00li5h]

browsers don't save things by default. that's how they are.

the thing in the interface that tells you that you're looking at a browser is up to you... in my mind, the address at the top, starting with http:// is the part of the UI that says my changes will be thrown away...

this is kinda why i'm miffed that there is an explicit "throw my changes away" button, when that's the default behaviour

[pbhjpbhj]

>"browsers don't save things by default."

// Depends on your browser.

[f00li5h]

when "submit form" and "save" are the same action, it doesn't depend on browser...

keeping it in cache/locally/whatever is not "saving".