There is an error in the design of the node edit form from a user interface usability perspective:

The Delete button is the last one.

That makes the Delete button very easy to be clicked, much more easier than Submit.

The expected design would be to have Delete as the middle button and Submit as the last button.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

TDobes’s picture

Project: Drupal core »
Component: node system » usability
cosmicdreams’s picture

Yes, this is definitely a usability issue. An alternative to the above suggestion would be to make Submit a button and delete a link. I think that's the way it is now. Am I wrong?

ximo’s picture

In Drupal 6-beta1 (what I have at hand), the buttons are in this order: Preview, Submit, Delete

I agree with nsk that this is bad design from a usability perspective, but not necessarily because of the order of the buttons, which is quite logical if you think about it (first you preview, then you submit, eventually you may delete). I think the issue with usability is that they all look exactly the same. See the paragraph on Primary & Secondary Actions here.

Styling the buttons could be done with CSS on the theme level, but on a code level, the button that has the primary action should be assigned a class indicating so. I also think the Delete button should be styled somewhat red, to clearly indicate that it does something horrible to the node ;)

ximo’s picture

I just realized that Preview is the default action for the Node form, which is a good thing! To let you know what I'm talking about, I've made a mockup of how the buttons could be styled. It can probably be done better, but it gives you an idea of how this could look.

elv’s picture

The order used here is what's almost always used on websites. It's because when you use the tab key, the first button you hit is the leftmost one. It follows the source order.
I think the default "submit" button should be the rightmost, and the destructive ones like "Delete" on the left (Mac style), but the tab order in browsers forces the opposite. Unless you float all of them right, that is, but this can be done at the theming level.

cosmicdreams’s picture

@ ximo: +1 for the change of styling on the delete button. Great idea

gaele’s picture

The article ximo links to suggests styling the delete button less prominent. This means faded instead of red.
It also suggests that the default button should be the first one (it "should vertically align with the input fields"). I don't know which button is default: preview or save.

So I like the idea of adding a class to the primary button, but I don't like the delete button being red.

elv’s picture

I'm with agele on this one. The delete button should be less visible, "greyed out". Red is the danger color, but it also attracts the eye. As the other buttons don't have a particular color, they would have less visibility.

ximo’s picture

I agree! Should've read the article more carefully :)

Grey it is!

ximo’s picture

Preview is the default action for the form, so it's in bold as you can see. It's also the left-most button which according to the article is correct.

(Had a typo in the filename of the latest mockup, should be "now" and not "not")

Anonymous’s picture

Project: » Drupal core
Version: » 7.x-dev

The user experience project is closing so this issue is being moved to the usability component under the Drupal project

heather’s picture

Component: usability » base system
FileSize
7.63 KB
9.28 KB

Looks fixed in the Seven theme. But it's not fixed in Garland or other theme.

I like the idea of the Preview and Save as buttons and Delete as text. What happened to that idea?

See screenshots attached.

In Seven admin theme:
seven-buttons.png

In Garland (or other without styling)
garland-buttons.png

Tor Arne Thune’s picture

Version: 7.x-dev » 8.x-dev
Category: bug » task
FileSize
5.2 KB

In my opinion this is a task, and not a bug. Also attaching a screenshot of the current state of the Node Edit form in Drupal 7 (using the Seven theme).
Bottom buttons on the node edit form in Drupal 7 using the Seven theme

dawehner’s picture

Component: base system » node system
Issue summary: View changes

.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final full bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)
FileSize
8.15 KB
6.06 KB

The node delete buttons are much different in 8.9.13.

On the a node page

And the node edit page

Based on that this has been fixed, closing as cannot reproduce.

As always, if that is wrong reopen the issue by setting the status to Active and explain what still needs to be done. Thx.