You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workflow action menu in the new edit mode does not properly adjust its width based on the longest action name in the menu. As a result, longer action names wrap unnecessarily, impacting the user experience.
Steps to Reproduce
Create a WF with a long name.
Open the edit mode of any content type with workflow actions.
Open the workflow action menu and observe that the menu width does not expand to accommodate the longest action name, causing text wrapping.
Acceptance Criteria
The workflow action menu should dynamically adjust its width based on the longest action name to ensure no unnecessary text wrapping occurs.
This can be either the button of the dropdown menu.
dotCMS Version
latest
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered:
Parent Issue
#31212
Problem Statement
The workflow action menu in the new edit mode does not properly adjust its width based on the longest action name in the menu. As a result, longer action names wrap unnecessarily, impacting the user experience.
Steps to Reproduce
Acceptance Criteria
The workflow action menu should dynamically adjust its width based on the longest action name to ensure no unnecessary text wrapping occurs.
This can be either the button of the dropdown menu.
dotCMS Version
latest
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: