Coming from a discussion here: #2163425: Automatically close the admin menu tray after using it on narrow screens I'd like to suggest it would be an improvement to the admin toolbar if it came with some configurable options.

The issue mentioned above is a good example, as some people will require the toolbar to always close after a menu link is clicked, others want it to close only on small screens. I think the admin module is a good example of how a few configuration options for admins create a lot more flexibility.

It might also be easier to make the toolbar much more customizable. Right now there are separate modules out in the wild that for instance allow other blocks/ menus to be added. But they need to be updated with each new release of the toolbar module. Imo it would be better to extend this module in a way where behaviors can be tweaked to the specific purpose of a project/ audience.

The toolbar is really beautiful and I can imagine people wanting to take more advantage of it, in various use cases.

Thanks!

Comments

AlfTheCat’s picture

AlfTheCat CreditAttribution: AlfTheCat commented
Issue summary: View changes
andrewmacpherson’s picture

andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commented
Issue tags: +Usability, +Accessibilty

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

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

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.

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.

andrewmacpherson’s picture

andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commented
Issue tags: +Accessibility

using preferred accessibility tag

andrewmacpherson’s picture

andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commented
Issue tags: -Accessibilty

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.

nod_’s picture

nod_
Primary language French
Location Lille
CreditAttribution: nod_ at Smile commented
Status: Active » Postponed (maintainer needs more info)

We wanted the toolbar to have no user-configuration, we had the toggle from vertical to horizontal but that is it. So it's not really the way the module was developped.

What kind of configuration options are we talking about, if we have an somewhat exhaustive list it'll be easier to discuss specifics and implementation if that's the way we're going.

In the state of things I'm not saying no, but it's not a yes either.

dww’s picture

dww
we/he/they
CreditAttribution: dww as a volunteer commented
Related issues: +#2801501: Option for the Toolbar *not* to auto-open the "Manage" sub-menu?

For example, #2801501: Option for the Toolbar *not* to auto-open the "Manage" sub-menu? would be a great global config option for a site that wanted to control that behavior (instead of applying the gnarly patch I have there now).

dww’s picture

dww
we/he/they
CreditAttribution: dww as a volunteer commented
Status: Postponed (maintainer needs more info) » Active

Added #1869638: Make the menu shown in the administration menu tray configurable as another child. That one has 2 other related on similar themes (possibly some duplicates).

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.

Pasqualle’s picture

Pasqualle
Location 🇭🇺 Budapest
CreditAttribution: Pasqualle as a volunteer commented

Drupal core should allow contrib to easily extend/modify its functionality. Currently the missing toolbar menu config is blocking the implementation of simple features in contrib, or at least making it overcomplicated.

nod_’s picture

nod_
Primary language French
Location Lille
CreditAttribution: nod_ commented

cross posting from #1869638-108: Make the menu shown in the administration menu tray configurable.

I'm not personally ready to support configuration (hidden or otherwise) for the toolbar module because it wasn't designed for it and I think the current situation, while not perfect, is good enough.

I wouldn't oppose someone stepping up that is ready to maintain this type of feature and deal with the associated maintenance it induces.

nod_’s picture

nod_
Primary language French
Location Lille
CreditAttribution: nod_ at Acquia commented
Version: 9.4.x-dev » 10.0.x-dev

To be clear, I'm asking for an additional maintainer, not someone to take up the whole module maintenance.

Before we start adding little pieces here and there of config I would prefer to figure out a plan (even a vague idea) about how this whole thing will work: what are we going to have configurable, with which granularity (sitewide, per user, per role?), are new permissions involved, how do we decide what should be configurable and what should not, etc.

toolbar is not an experimental module so once we release something it's stable and we can expect contrib to rely on it, it also means that changes will need a BC layer, and we've seen it's great for users but it's a lot of work on the maintenance side of things. Since it's new it's probably going to change a bunch of times before we get it just right (while keeping a minimum of a BC layer), this will introduce churn in core and in contrib. To avoid frustration someone should be a point of contact for this to centralize the knowledge and I don't have the will/time to do this work at the moment, which is why I'm looking for someone who does.

Pasqualle’s picture

Pasqualle
Location 🇭🇺 Budapest
CreditAttribution: Pasqualle as a volunteer commented
Version: 10.0.x-dev » 10.1.x-dev

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.