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
MenuSection used component={Fragment} on MUI MenuItem when items had no link prop. React's Fragment silently drops all props, so MUI's role="menuitem" and tabIndex attributes were never rendered to the DOM. This made those items invisible to MUI MenuList arrow-key traversal. The Help dropdown's SupportButton (which manages navigation internally and has no link in its mount point config) was the primary victim.
The fix conditionally spreads component/to only when a link exists, letting MenuItem render its default <li> with proper ARIA attributes. Non-clickable section headers now render <ListSubheader> directly instead of wrapping in a no-op <MenuItem component={Fragment}>.
Fixed
RHDHBUGS-1931 — [global-header] Menu items in Help menu can't be accessed with a keyboard
Checklist
A changeset describing the change and affected packages. (more info)
Added or Updated documentation
Tests for new functionality and regression tests for bug fixes
Screenshots attached (for UI changes)
Note
This bug fix was identified and implemented using the bug-fix and raise-pr agent skills. Please verify the fix thoroughly before merging.
❌ Patch coverage is 40.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.26%. Comparing base (8d3503a) to head (b91b377). ⚠️ Report is 36 commits behind head on main.
✅ All tests successful. No failed tests found.
/hold
Lets wait for accessibility fix of global-header by @rohitratannagar then we will revisit and check ifwe still need this PR.
Cc: @sanketpathak@teknaS47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
MenuSectionusedcomponent={Fragment}on MUIMenuItemwhen items had nolinkprop. React'sFragmentsilently drops all props, so MUI'srole="menuitem"andtabIndexattributes were never rendered to the DOM. This made those items invisible to MUIMenuListarrow-key traversal. The Help dropdown'sSupportButton(which manages navigation internally and has nolinkin its mount point config) was the primary victim.The fix conditionally spreads
component/toonly when a link exists, lettingMenuItemrender its default<li>with proper ARIA attributes. Non-clickable section headers now render<ListSubheader>directly instead of wrapping in a no-op<MenuItem component={Fragment}>.Fixed
Checklist
Note