Problem/Motivation

Input format field getting displayed inconsistently depending on the permissions. Here are the scenarios:

1. When user has only basic filter (i.e "Use the Basic HTML text format" permission), the input format field disappears from the display, but leaving help text:

2. When user has only only restricted html filter (i.e. "Use the Restricted HTML text format" permission), the input format field displays both basic and Restricted

Proposed resolution

It's open for discussion how best/consistent we can make it so the it wouldn't confuse the content editor. Here is some options:

For scenario 1, we should at least have the format details as text (without dropdown).

For scenario 2, I understand "Restricted HTML" means we can have basic as well, but system doesn't necessary need to decide that. This way, we can avoid dropdown when only one filter is enabled for given user/role.

Steps to reproduce

1. Create a role with all article add/edit/delete permissions and "Use the Basic HTML text format" permission
2. Create a user and assign this new role
3. Login as the user created in step 2 and visit node/add/article

Remaining tasks

1. Discuss

User interface changes

Mostly depending on the solution

API changes

N/A

Data model changes

N/A

CommentFileSizeAuthor
basic-and-restricted.png102.76 KBvijaycs85
only-basic.png81.07 KBvijaycs85
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

vijaycs85 created an issue. See original summary.

Dinesh18’s picture

Dinesh18 CreditAttribution: Dinesh18 as a volunteer commented

Yes. It would be a good option to have no drop-down when only one filter is enabled to avoid confusion.
But I wonder if we should consider this as bug or Task ?

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett at Acquia commented
Component: forms system » filter.module

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.

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Version: 9.4.x-dev » 10.0.x-dev
Status: Active » Closed (cannot reproduce)
Issue tags: +Bug Smash Initiative

I tested this on Drupal 10.0.x, standard install, and when a user has only the restricted HTML filter there is no drop down with both basic and restricted.

Therefore, closing as cannot reproduce. If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").

Thanks!