On Thu, Jul 30, 2009 at 21:41, Cian OConnor<[email protected]> wrote: > If the situation is one in which the user has simply lost interest in > the original task, then what they'll be looking for is a route back to > whatever they were doing previously. In which case "cancel" is confusing > and meaningless (what will "cancel" do? Will it clear the form? Take me > to the home page).
Why should 'cancel' clear/reset the form (in HTML there's even a special 'reset' button for this – one that is IMHO 99.9% useless)? Why should 'cancel' take one to the home page? Designs that do so should ASAP cease to exist. Personally, I'd expect 1) to be taken back to were I initiated the action calling up the form and 2) that any data entered would not persist. And I've yet to encounter anybody having trouble with the implementation of this. :-) > If the situation is one in which the user has started a transaction of > some kind, then what they really want to do is kill that transaction > to make sure it doesn't persist, OR they may wish to save the > transaction for later, or whatever. Here "Return to X" isn't going to answer > their > question and is therefore unclear and confusing. I second that. On a side note, as this came up in one of the other posts: I would never rely on the browser's back button for navigation. Believe it or not, but I've seen far too many people practically never use them. Sascha Brossmann -- &:create ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
