On Tue, 2009-07-07 at 09:45 +0100, Andy Baker wrote: > Mmmm. That's a fair point but that article was written before web > applications were so application-ey and expectations may well have > changed. (I've noticed a lot of semi-modal dialogs in web apps > complete with 'cancel' buttons and with javascript dialogs the back > button doesn't do what Jakob implies people expect) > > So there is a lot of subtlety here and I'd like to get more data. It > never occurred to me that Cancel was needed until I watched a user > flounder when they didn't know how to get out of the change screen. > > > Usability experts disagree with you vehemently: > > > > http://www.useit.com/alertbox/20000416.html > > > > Cheers > > > > Tom > > > >
In this case though, it is not a modal dialogue box, it is a large form, with a bunch of form inlines, much like a lot of other web pages. The advice may be old, but it is still valid. Cancel buttons can bring a lot of confusion to the mix, particularly when you actually start doing application-style things like AJAX modification of the models, (some) users will expect the cancel button to revert all changes you've made since loading the page (including committed changes made through AJAX). It just gets more confusing for the average user to understand. Cheers Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
