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
Currently, the body of the message components in '@fluentui-contrib/react-chat' are considered tabbable elements. However, when the actions component is specified for my message FluentUI component, it is added at the same level as the body component. This breaks the keyboard navigation hierarchy, as both the actions and message body are on the same level. As a result, actions are accessible with the Tab key instead of the Enter key.
Steps to Reproduce:
Use '@fluentui-contrib/react-chat' to create a chat interface.
Add actions buttons list
Specify an actions component at the same level as the message body.
Attempt to navigate using the keyboard.
Expected Behavior: The actions component should be accessible with the Enter key, maintaining a proper keyboard navigation hierarchy.
Actual Behavior: The actions component is accessible with the Tab key, disrupting the expected navigation flow
The text was updated successfully, but these errors were encountered:
It looks like this can be updated by using ...useFocusableGroup({ tabBehavior: 'unlimited' }) and handling Enter key locally. But please let me know if there is a better solution for this.
UPD: it looks like it's not a very good approach as it changes the browsers keyboard navigation too much
Currently, the body of the message components in '@fluentui-contrib/react-chat' are considered tabbable elements. However, when the actions component is specified for my message FluentUI component, it is added at the same level as the body component. This breaks the keyboard navigation hierarchy, as both the actions and message body are on the same level. As a result, actions are accessible with the Tab key instead of the Enter key.
Steps to Reproduce:
Expected Behavior: The actions component should be accessible with the Enter key, maintaining a proper keyboard navigation hierarchy.
Actual Behavior: The actions component is accessible with the Tab key, disrupting the expected navigation flow
The text was updated successfully, but these errors were encountered: