Updated: Comment #0

Problem/Motivation

The form at the top of admin/people is currently a bit chaotic and confusing:
screenshot of the admin/people form

The local action to add a user is not clearly delineated from the rest of the form, and the difference between the exposed filters and the action selection isn't clear. Additionally, having the Apply button below its select box but the Filter button inline makes the form look sort of imbalanced.

Proposed resolution

We should add better visual and semantic separation between the three parts of this form

#1475204-17: [META] Provide a generic search/filter UI interface pattern for listing pages proposes a fairly dramatic overhaul to the interaction, but it would require significant API changes for exposed filters that are unlikely to make it into D8. Let's see if there's any semantic markup and layout adjustments we can make to make this more usable and accessible.

Remaining tasks

  1. Come up with a design (preferably just form/markup/CSS changes?).
  2. Create patch.
  3. Usability review
  4. Do accessibility testing.
  5. Apply the same pattern to admin/content.

User interface changes

TBD

API changes

TBD

CommentFileSizeAuthor
#7 Redesign Filters in Add People.png95.75 KBaroop_1987
#2 Snímek obrazovky 2013-09-24 v 16.08.17.PNG28.32 KBhonza pobořil

Comments

tkoleary’s picture

tkoleary commented

@xjm

Also relates to #2022297: [META] Unified toolset for Views in core

honza pobořil’s picture

honza pobořil commented
StatusFileSize
new Snímek obrazovky 2013-09-24 v 16.08.17.PNG28.32 KB

Too think about all these Apply buttons (see attached screenshot). I am lost too what button do what.

honza pobořil’s picture

honza pobořil commented
Issue summary: View changes

Updated issue summary.

tkoleary’s picture

tkoleary commented
Related issues: +#2346973: Improve usability, accessibility, and scalability of long select lists

This would be an excellent place to use Select 2.

yoroy’s picture

yoroy commented
Version: 8.0.x-dev » 8.2.x-dev

This is something to prototype maybe?

yoroy’s picture

yoroy commented
Parent issue: » #2721807: Design for filters and bulk operations

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

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.

aroop_1987’s picture

aroop_1987 commented
StatusFileSize
new Redesign Filters in Add People.png95.75 KB

There 3 main changes i made in this wire frame:
1. Binding the filters section inside a container to clearly differentiate it.
2. Replacing Selection Boxes with Check boxes.The reason behind this is to avoid making the user guess on options due to select boxes. Also this gives user more control to refine the filtering.
3. Binding BULK ACTIONS with table, as it is the most immediate action after selection in the list. DELETE and ADD ADMINISTRATOR ROLE can be a part of Bulk Operations.

tkoleary’s picture

tkoleary commented

@aroop_1987

Interesting approach.

I still think that there is no better pattern for this than dismissible pills like those provided by chosen or select2.

Checkboxes work well if there is a limited set of available options, but there are many instances where the set of options is quite large and checkboxes just don't scale.

wturrell’s picture

wturrell commented

[edited to be more helpful]

I agree about how using checkboxes often leads to clutter…
Btw there is/was a select2 module...

Taking a step back – I'm not convinced this issue is still relevant (@xjm?)
Caveat: I had barely heard of Drupal when it was created.

In 8.2.x /admin/content is a near copy of /admin/people and they're both user configurable views, and also the stylesheet has changed somewhat since the screenshot.

@aroop_1987 you might want to get involved with either of the two meta issues.

Quoting from the issue summary:

- "The local action to add a user is not clearly delineated from the rest of the form" - not sure I agree, the button style and top-of-page position seems consistent with other forms; as a relatively new user I still feel I recognise a blue button with a + sign is going to take me to a new form/page
- "and the difference between the exposed filters and the action selection isn't clear" - since then the button text has been changed from 'Apply' to 'Apply to selected items'
- also this is no longer the case: "Additionally, having the Apply button below its select box but the Filter button inline makes the form look sort of imbalanced."

I'd be minded to change this to "Closed - outdated" if there's consensus on all that...

tkoleary’s picture

tkoleary commented

Screenshot in summary is out of date. Shows Drupal 7.

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

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.

ckrina’s picture

ckrina
she/her
Primary language Catalan
Location Barcelona
commented
Status: Active » Postponed

I'd like to pospone the development here until a generic & integrated design for VBO and filters has been decided. See #2721807: Design for filters and bulk operations.

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

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). 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.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Category: Bug report » Task
Issue tags: +Bug Smash Initiative
Related issues: +#2755613: Restructure the admin interface Information Architecture, +#2695771: Re-organise user/account items under admin/

Reading the Issue Summary and comments this is not a bug so I am changing this to a task.

Adding related issues found when looking for duplicates.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed » Active

This issue has been postponed on #2721807: Design for filters and bulk operations, but that issue is now for the contributed Seven theme. That issue should no longer block a Drupal core issue; eventually, it should be #2721807: Design for filters and bulk operations that is postponed on this issue.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Parent issue: #2721807: Design for filters and bulk operations »

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.