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
If focusMode = 'tab-only', and the Card has an event handler (especially 'onClick'), then focusMode regresses to no-tab behaviour (which is both undocumented and unexpected). This behaviour is introduced here.
Actual Behavior
When the card is focusable, onClick event handlers are not allowed and adding them regresses the focusMode to no-tab.
Expected Behavior
When the card is focused, onClick event handlers should be supported. As well as the onKeyDown/onKeyUp for pressing Enter which should match the onClick behavior.
Logs
No response
Requested priority
Normal
Products/sites affected
Microsoft Loop
Are you willing to submit a PR to fix?
no
Validations
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
The provided reproduction is a minimal reproducible example of the bug.
The text was updated successfully, but these errors were encountered:
I have experience the same behavior... would be nice to fix it...
when it is "tab-only" focus mode, then Enter should bring user focus inside the card...
Library
React Components / v9 (@fluentui/react-components)
System Info
Are you reporting Accessibility issue?
yes
Reproduction
https://stackblitz.com/edit/4g3qid?file=src%2Fexample.tsx
Bug Description
If
focusMode = 'tab-only'
, and the Card has an event handler (especially 'onClick'), thenfocusMode
regresses tono-tab
behaviour (which is both undocumented and unexpected).This behaviour is introduced here.
Actual Behavior
When the card is focusable,
onClick
event handlers are not allowed and adding them regresses thefocusMode
tono-tab
.Expected Behavior
When the card is focused,
onClick
event handlers should be supported. As well as theonKeyDown
/onKeyUp
for pressing Enter which should match theonClick
behavior.Logs
No response
Requested priority
Normal
Products/sites affected
Microsoft Loop
Are you willing to submit a PR to fix?
no
Validations
The text was updated successfully, but these errors were encountered: