Problem/Motivation

New users (and even some seasoned users) can be under the impression that once they have finished changing a permission, or placing a block or some such, that they are done, without even realizing that way down on the page is a save button that they must hit to complete the task.

On some really long pages the "Save" button is buried off screen, and if for instance they just wish to place a block in the header region, they never see it.

P.S. I am not sure if "Base System" is the correct component for this or should it be against Seven theme??

Proposed resolution

Add to the help text that they must hit save to complete the action. And place a second "Save" button at the top right of the page.

Remaining tasks

Evaluate all our admin pages and add extra "Save" button where appropriate.

User interface changes

Extra save button and some helpful text.

API changes

None

Data model changes

None

Comments

cilefen’s picture

Component: base system » user.module

It is the user module.

mbrett5062’s picture

I think you have missed the point a little. I am referring to not just the permissions page.

This problem is also in the block module, menu module, and modules system.

It is anywhere we have a long form, with a submit action that is only shown at the bottom of the form.

A lot of what we are doing does not require the complete scan of the whole form, so many times the bottom of the page will not be seen.

Some of these pages say that you must click the save button at the bottom of the page to complete the task (See block layout) but not all.

I just think that from a usability perspective, there is no harm in a save button both at the bottom/end and at the top/beginning of the form.

Lets help our users where we can.

mbrett5062’s picture

Maybe I need to do the research myself and open a new issue for each module/system?

cilefen’s picture

Component: user.module » base system

There was recently a usability study. Check over their findings because those issues are prioritized, but maybe bring this up as an issue to the folks that are working on it:

#2497361: [meta] Fix issues found during UMN Usability Testing 2015

mbrett5062’s picture

Will create separate issues and see how to get into usability study information, or at least bring it to the attention of the organizers on Monday.

cilefen’s picture

There is no need for separate issues yet.

tim.plunkett’s picture

In D7, the Views UI had the Save button at the top, and not at the bottom. Consequently, people missed this button often.
When adding it to core, I wanted to have it at the top *and* bottom, but it was just moved to the bottom.

Just giving some precedence for it being at the top.

mbrett5062’s picture

Aside from Drupal, I have also been using Processwire a lot recently, and all their admin forms/pages that have an action button place it at both bottom left and top right. It just seems so much more convenient.

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.

yoroy’s picture

Issue tags: +ux-workflow

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.