Make configuration of text formats more secure by default

Created on 8 November 2012, over 12 years ago
Updated 15 March 2025, about 2 months ago

Problem/Motivation

In πŸ“Œ Consolidate filter options in the UI when configuring a format Postponed: needs info , we're trying to improve the UI for configuring a text format. One of the most confusing parts of configuring a filter is figuring out the "Filter order" options. To new users, these the filter order is baffling. Even experienced users sometimes need to grok code or parse through several modules' README.txt files to figure out the proper order for things.

Proposed resolution

Research and evaluate ways that we can make filter order more predictable for contributed modules to be "secure by default". Right now modules are able to provide a default weight for their filter, but that default is completely worthless once a user has rearranged the filters on a text format and then enables a new filter. After increasing the security of filters by default, consider reducing the prominence of the filter order, such as relegating it to a vertical tab, collapsed fieldset, or another approach.

Remaining tasks

Brainstorm, discuss, implement.

User interface changes

Reduce the prominence of filter order if we can ensure security by default.

API changes

TBD.

✨ Feature request
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.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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 sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. 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