Consolidate filter options in the UI when configuring a format

Created on 7 November 2012, over 12 years ago
Updated 10 February 2025, 13 days ago

Problem/Motivation

I summarize the problem (and suggestion) in this video: http://screencast.com/t/YSQ5KnFTtP

  • Page help text describes filter processing order, but actual filter processing order is not visible yet (it's far down on the page).
  • Enabling or removing filters does not make it clear that new options are being added or removed fromt the page (cut off by scroll bar again).
  • Filter processing order is featured too prominently and too early on the page.
  • With no filters enabled, we have an empty vertical tab set. This happens commonly when configuring a new format.

Proposed resolution/UI Changes

Move filter enabled list into the vertical tab set as the first tab. Move the filter order into the vertical tab set as the last tab. Move the description of the filter ordering to be the description of the filter order, instead of the top of the page.

Remaining tasks

This issue is intended as a precursor to #1833716: WYSIWYG: Introduce "Text editors" as part of filter format configuration β†’ , which ultimately would add WYSIWYG configuration to the format configuration page, so we need to optimize the settings on this page before we add more options. However this issue is not dependent upon it. The changes help with the UI even if we don't add the WYSIWYG editor settings on this page.

API changes

None.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

filter.module

Created by

πŸ‡ΊπŸ‡ΈUnited States quicksketch

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024