I'd like to use it for hiding permission descriptions, Keith Smith wants to use it for hiding help text, and one could probably think of another half a dozen places in Drupal it could be useful. Right now the "turn descriptions on and off" link is a) coded to always redirect to the ?q=admin page, b) not displayed on any other pages.

So let's genericize this (if that's a word) so that any admin page can have its details hidden.

Comments

gaele’s picture

gaele commented

one could probably think of another half a dozen places in Drupal it could be useful

Yup, like toggle the display of field descriptions.

I'm thinking about three options, so a user could adjust the display to his/her own experience level:

- off
- on (inline)
- on (pop-up)

And IMHO this should not be constrained to just the admin pages. On the node add page it could be useful too.

(BTW also see this discussion about help pages in pop-ups.)

gaele’s picture

gaele commented
Title: Genericize "Hide descriptions" link » Generalize "Hide descriptions" link

And yes, this "Hide descriptions" link should be "genericized" ;-)

Where to put this link? Think about this: "hide help/descriptions" is not a navigation link, it is a utility link, just like e.g. "logout".
A nice place would be in the upper right corner. (See e.g. admin_menu module, and Steve Krug's book "Don't Make Me Think").

lilou’s picture

lilou commented
Component: system.module » usability

bump

gaele’s picture

gaele commented
Component: usability » system.module
Issue tags: +Usability
catch’s picture

catch
he/him
Primary language English
commented

Nice idea.

andypost’s picture

andypost
he/him
Primary language Russian
commented

duplicate #202593: 'Hide descriptions' link on admin/config affects other pages

Also there's a critical issue #748976: "Show/hide descriptions" links no longer work

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Version: 7.x-dev » 8.x-dev
andypost’s picture

andypost
he/him
Primary language Russian
commented
Issue summary: View changes
Related issues: +#202593: 'Hide descriptions' link on admin/config affects other pages

Seems this should go to 8.1.x now, also there's collision with related

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.

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.

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should 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: 9.5.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. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

mstrelan’s picture

mstrelan commented
Status: Active » Postponed (maintainer needs more info)

Is this still relevant? There has not been an update in over 10 years.

I did some digging to see what this is about. There is a system.admin_compact_page route that sets the admin_compact_mode cookie. There is also a system_compact_link render element to generate a link to toggle this cookie. This render element is currently used on "administrative index page templates" via template_preprocess_admin_page and "admin index templates" via template_preprocess_system_admin_index. Example URLs are /admin/index and /admin/config.

The issue summary mentions #30984: Usability: Provide descriptions for permissions, but it seems we're already using the same link in \Drupal\user\Form\UserPermissionsForm::buildForm. It also mentions #205226: Use system_admin_compact_mode to hide $help text which has not been done. Perhaps this should be converted to a meta and the two issues mentioned should be child issues.

From my POV I've never used the link or noticed that exists, so I don't have strong feelings towards this. My expectation would be that users have a preferences page linked to their account, rather than a cookie, and they could toggle on descriptions and help text from there.

Changing the status to PMNMI until we know if this is something we want to follow up.

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there's been no follow up in 6 additional months and was a feature request that didn't seem heavily desired going to close out. Can always be re-opened

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.