[Bug]: Keyboard focus loss in Carousel when there are only 2 CarouselCard

[xunkai]

Component

Carousel

Package version

9.58.3

React version

17.0.1

Environment

System:
    OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD EPYC 7763 64-Core Processor
    Memory: 57.74 GB / 62.79 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Browsers:
    Chrome: 135.0.7049.52

Current Behavior

Keyboard focus loss in Carousel when there are only 2 CarouselCard. See video below

Fluent_carousel_bug.mp4

Expected Behavior

The keyboard focus will not lose and will focus on the previous button

Reproduction

https://stackblitz.com/edit/efrqonjj?file=src%2Fexample.tsx

Steps to reproduce

1. Click 'tab' by keyboard to focus on Next button
2. Click 'enter'
3. The focus is loss

Are you reporting an Accessibility issue?

yes

Suggested severity

Urgent - No workaround and Products/sites are affected

Products/sites affected

No response

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.

[dmytrokirpa]

I'm a bit unsure about where the focus should go when the user gets to the first or last slide, and the Next/Prev buttons are disabled.

Could you please check this, @Mitch-At-Work, and re-assign it to someone from your team or @microsoft/teams-prg?

[mathis-m]

I'm a bit unsure about where the focus should go when the user gets to the first or last slide, and the Next/Prev buttons are disabled.

Could you please check this, @Mitch-At-Work, and re-assign it to someone from your team or @microsoft/teams-prg?

I do not think that this needs further discussion as this is already implemented. But not working as expected:

On click/invoke of a button the focus is getting fixed already based on:

• Clicked on first or last based on direction
• Not circular

The issue here is that as of the point the button is invoked the other button is disabled (for the case where there are only 2 slides).
This is an oversight in the implementation itself.

I will go ahead and create a PR