Drupal Usability Meeting 2026-03-20

added a few points about content moderation in general we've touched today. feel free to add as well as update the list in the issue summary. the points are in no particular order yet.

This is the behavior of the Navigation module. IMO, it should be under the control of the theme, not any module. For now, it is still possible to uninstall navigation and install toolbar. You can even install the contrib admin_toolbar.

in the admin ui the navigation module shouldnt interfere in the first place. those local tasks are strictly speaking navigation and not CTAs. i understand the step in the front end for theming purposes but in the backend not the best idea. plus everything is cramped into that "more actions" list. that list is in the upper right corner of the screen. if you have a large widescreen like me and pull browser windows wide, your focus is on the node edit form and then your focus / eyes have to move a long way to the upper right corner. while if the local tasks would still be shown they would be right underneath the h1, plus they would provide direct context in which section of a node a user currently is.

This seems like such a serious bug that I think we have to understand it before considering the related problems. But it seems to be a known bug when both content_moderation and workspaces are enabled: #3541380: Node edit form always uses published revision when using content_moderation and workspaces. (I keep looking at workflows, which is required for content_moderation, and misreading it as workspaces.)

i think most likely the node edit form showing the published version instead of the revision while workspaces is enabled is a different bug than the pressing the "set as current revision" on forward revision again triggering a confirmation form for another revert.

If you want to see differences between revisions, then you can install the contrib Diff module.

no this point wasnt necessarily about the diff (i've mentioned the diff only as an additional useful information). but when you are on a node edit form it lacks context, am I on the default, a forward or a past revision? and in case one is on a forward revision something like a toggle button for displaying the default version alongside to illustrate the changes in context (that was the reason why I've added the detail about diff). but as i said first of all it is important to provide the context on what type of revision i am on. at the moment the only information available is that this is a revision (and revisions are required), when the node was last saved, and the current state and the select element to choose which state to switch the node to. but it lacks more context

and was it by accident or intentional that you removed the collection of potential issues section in the issue summary and removed the del tags from the point about granted issue credits and the issue discussed?

fixed the broken link in the issue summary pointing to the transcript

I'll readd the points for direct reference to this comment:

Collection of potential issues

• Drop buttons on nodes on admin/content are missing Revisions as an option - the applies to admin/content/moderated as well. The user has to go press the edit button for a node and within the node edit form press the more actions button to get to the revision local item
• Drop buttons on the revisions page for a node miss the option to edit aka to directly get to the node edit form of that revision
• set as current revision is doing the same as the Revert button. for forward revision revert shoulnd't be used but publish should be used instead directly
• on node edit forms, user edit forms (and which other entity types) local task are removed and displayed as options in the more actions button. in the front end that is ok but in the admin ui the cognitive load is higher
• on a node edit form you don't see the revision of that node. if it is a forward, a past or the default revision. in case it is a forward or past revision there is also no link (to for example a diff) to the default revision
  https://www.drupal.org/project/drupal/issues/3371457
• the revisions list page does not provide much situational awareness to the user. the only anchor is the label "current revision" for the default revision, aside that the sole differentiator is the date and time stamp. - at the very least each revision needs the revision number, publishing status, and the state
• there is no cue that there is one or more new entities under admin/content/moderated that need the attention of the currently logged in user. The differentiation between "overview" and "moderated content" is also tricky. In the first meeting we discussed this MR we solely stayed on the "overview" secondary local task and missed the "moderated content"
• use a dialog modal for confirmation step for core in general

comment with the summary of the meeting at: #2906568-120: Provide users with the option to select an appropriate moderation state when reverting to a previous revision