v15.4 Responsive Behavior for Workspace Action Container on Smaller Screens

[jbppraxis]

Which Umbraco version are you using?

15.4

Bug summary

We have extended the Umbraco CMS workspace action area by adding custom buttons. While this functionality works as expected on larger screens, we've observed that the action buttons overflow the container and become partially or completely obscured on smaller screens (e.g., mobile devices).

The current behavior presents a usability issue, as users may not be able to access all available actions on smaller screens.

Is there an existing configuration option or recommended approach to ensure the workspace action container adapts responsively to different screen sizes? Ideally, the container should dynamically adjust its layout (e.g., through wrapping, scrolling, or other responsive techniques) to ensure all action buttons remain visible and accessible, regardless of the screen size.

Specifics

No response

Steps to reproduce

1. Add multiple custom action buttons to the action workspace. A minimum of 5-6 buttons is recommended to reliably reproduce the issue.
2. Open umbraco
3. Reduce the browser window width (or use a device with a smaller screen) to simulate a smaller screen size. Observe the behavior of the action buttons within the container.

Expected result / actual result

Expected result: The action buttons should remain fully visible and accessible, either through wrapping, scrolling, or another responsive mechanism.
Actual result: The action buttons overflow the container and are partially or completely hidden.

[github-actions]

Hi there @jbppraxis!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[github-actions]

Hi @jbppraxis,

We're writing to let you know that we would love some help with this issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post.

Thanks muchly, from your friendly Umbraco GitHub bot :-)

[nielslyngsoe]

Hi @jbppraxis

Super interesting and well spotted, we should support this so it works when running on a small screen.

We do not have a solution for you currently, I see you are already using the Workspace Action Menu Items on the Gutenberg handlinger which enable you to compose multiple actions into one. But we do not have anything that handles button overfloats.

One solution would be to copy the logic from tabs, where the tabs that do not have space on the screen go into a dropdown (with the symbol '...') see uui-tab-group for reference.

Otherwise a sideway scroll is also an option, but it could visually be hard to grasp as we have the breadcrumbs etc in the left side, meaning that the buttons does not have the full width for their scroll container.

I've marked this as up-for-grabs as I want you and others to know that we accept inputs on how this should be resolved.
Please keep Accessbility in mind.