Closed (won't fix)
Project:
Social Forum Call for Action
Version:
5.x-.1.x-dev
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Reporter:
Created:
8 Nov 2007 at 06:18 UTC
Updated:
5 Apr 2008 at 23:00 UTC
in all the form there is no “ cancel “ button –
one has to “go back” – is it clear enough ? ?
in the case of editing an existing content -there is always the bad impulse to click on " delete" when looking for "cancel"
Comments
Comment #1
mlncn commentedI'd like a little more usability discussion on this.
If anything, we would lean toward a cancel link rather than a cancel button to make it less likely to be pressed by accident.
Very good point on Delete being where people may expect a Cancel, however most participants for most content will not have delete privileges. Also, clicking delete always takes one to a confirmation page.
Comment #2
mlncn commentedComment #3
mlncn commented[EDIT: deleted. Comment wasn't showing up for me, so I triple posted!]
Comment #4
mlncn commented[EDIT: deleted. Comment wasn't showing up for me, so I triple posted!]
Comment #5
mlncn commentedWon't fix, we're going to trust the wisdom of Drupal on where it uses Cancel buttons, and where it chooses not to.
Wonder if this will come up in the Season of Usability starring Bevan Rudge.
benjamin, Agaric Design Collective
Comment #6
byteslinger commentedThe browser back button is indeed the proper tool for most "Cancel" functionality. But I have had several users get frustrated because they are not sure what to do next when they don't want to save changes they've made on a form or are afraid to click a "Delete" button. I advise using it sparingly, and only for user convenience, but here is a simple Cancel button that seems to work well on my Drupal forms:
$form['cancel'] = array(
'#type' => 'button',
'#value' => t('Cancel'),
'#attributes' => array('onClick' => "form.action='javascript:history.back(-1);'"),
);