Problem/Motivation
On edit forms under admin/content, admin/content/block, admin/content/media, as well as on user pages under user/[uid] the local items are getting removed from the page and moved as option into the top bars More action button in the upper right corner of the page.
For the front end, when you view one of the corresponding entity pages, it is a reasonable step to remove the local items and move them into the More action button to avoid any theming related issues - so you don't have to deal with any components themed by another theme in the active front end theme. In the context of the admin theme however, that measure is potentially confusing and challenging to the user - the cognitive load gets increased significantly.
- It breaks with the pattern users are familiar from other entities and pages within the admin UI. Those local tasks provide the user the situational awareness about the structure of an entity plus which of the local tasks at hand is the active one. At the moment you have to chop yourself together that bit of information via the breadcrumb, and the URL in the browser - which of the options however is the active one in the
More actionbutton is not really communicated at all. Plus the order of options differs, in case ofEditbeing the active option for for example a content type, the option is getting moved out to a dedicated button and the order and number of options for theMore actionbutton changes. - The
More actionbutton itself is really hard to spot (see #3540337: Improve visibility of More actions menu button). By removing the local task and having a dedicated button you are barely able to notice, that button gets sort of out of sight and out of mind easily - I always tend to forget myself that there is theMore actionon a widescreen monitor. There is the feeling of isolation and that the entity got stripped of its structure. In addition to that, you have all the time, except for theEditpage is the current page, one additional click to reach that list of available options for an entity. - One additional problem that also applies to the local tasks strictly speaking, local tasks as well as the options in the
More actionbutton are masked objects, they provide no additional cues to differentiate them in a glimpse of an eye. The user has to thoroughly read the labels each and every time to be sure.
It was part of a set of problems identified during #3578994-12: Drupal Usability Meeting 2026-03-20. The attendees were: @benjifisher, @pallavi singh3013, @rkoller, @simohell, @the_g_bomb, and @worldlinemine.
Steps to reproduce
- Go to
admin/content,admin/content/block,admin/content/media, and/oruser/[uid]and expand the context menu for theMore actionbutton in the top bar - Go to
admin/structure/types, create and edit a content type, and compare that content type with one of the previous pages for an entity or user.
Proposed resolution
For every page in the context of the default theme keep the current behavior and keep local tasks as options within the More action button
For every page in the context of the administration theme local tasks should be moved to the content header again right underneath the h1 - the More action button should only contain additional actions / CTAs that are no local tasks.
There should be a check that hides the The empty menu is a preexisting problem (eg, at the user view page More action button if it contains no options, like it already happens in case of the view page for a user page./user/*). @rkoller and @kentr discussed making the check for the empty menu a followup.

Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3590502
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
rkollerComment #3
rkollerComment #4
kentr commented+1 to this.
As a regular user who's not well-versed in the finer points of UX, I've found this menu to be unpredictable and baffling. @rkoller and I were discussing the case where it's empty and wondering what is causing that.
It's not empty when you're on the Edit page, so presumably the problem is because the "Edit" option is permanently moved out of the menu and the active menu item is also removed.
So to go to the "Edit" page, you click the button in the top bar. But to go to the "View" page, you open the menu. It doesn't make sense to me.
Comment #5
mortona2k commentedHere is a module that can modify local task/action settings, including preserving the local tasks in place on all or specified pages.
https://www.drupal.org/project/manage_top_bar
This provides a workaround for many top bar issues being discussed, and can help experiment to figure out the UX we want.
Comment #7
kentr commentedComment #8
kentr commentedThe MR removes local tasks from the More Actions menu, with the exception of one for Layout Builder because tests fail without that.
The Layout Builder item is hidden elsewhere, which results in an empty More Actions menu rendered on the page.
The empty menu is a preexisting problem (eg, at the user view page
/user/*). @rkoller and I discussed making the check for the empty menu a followup.Comment #9
smustgrave commentedFine with moving empty menu to a follow up but think that should happen first right? With this MR seems worst now that we get an empty menu. Thoughts?