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
Describe the enhancement or change
This is a spike to investigate potential ways to allow customizing the auto-focus that occurs when a Menu/menu-like component is triggered open. Followup from an async convo on Slack in regards to #10393.
Some quick thoughts:
We could look into extending the new prop added to Select, shouldFocusFirstMenuItemOnOpen, to Dropdown and/or Menu
We could allow passing a custom element to focus for Dropdown and Select, e.g. instead of our internal click handlers that will run firstElement.focus().
We could update KeyboardHandler logic in Menu in some way (either trimming the list of querySelectors in the getFocusableElement prop (~line 305 of Menu file) or allowing passing a custom querySelector
A secret 4th option (aka whatever else may be found in investigation)
We should also consider whether any such updates should apply to all 3 of these components (Select, Dropdown, Menu), or only some, and whether we want to recommend that Dropdown/Select only have valid [Dropdown | Select]Option components, and anything more custom requires a manually/custom built Menu implementation.
Once it's decided which route to go, we should close both this and 10393, and open a new issue to iterate on a resolution.
Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?
Any other information?
The text was updated successfully, but these errors were encountered:
Describe the enhancement or change
This is a spike to investigate potential ways to allow customizing the auto-focus that occurs when a Menu/menu-like component is triggered open. Followup from an async convo on Slack in regards to #10393.
Some quick thoughts:
shouldFocusFirstMenuItemOnOpen
, to Dropdown and/or MenufirstElement.focus()
.getFocusableElement
prop (~line 305 of Menu file) or allowing passing a custom querySelectorWe should also consider whether any such updates should apply to all 3 of these components (Select, Dropdown, Menu), or only some, and whether we want to recommend that Dropdown/Select only have valid [Dropdown | Select]Option components, and anything more custom requires a manually/custom built Menu implementation.
Once it's decided which route to go, we should close both this and 10393, and open a new issue to iterate on a resolution.
Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?
Any other information?
The text was updated successfully, but these errors were encountered: