Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: LineChart callout not automatically closed when navigating in backwards direction #33528

Open
2 tasks done
mercadoj32 opened this issue Dec 30, 2024 · 0 comments
Open
2 tasks done

Comments

@mercadoj32
Copy link

Charting Control

LineChart

Package version

5.23.20

React version

18.3.1

Environment

System:
  OS: Windows 11 10.0.26100
  CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Memory: 11.65 GB / 31.71 GB
Browsers:
  Edge: Chromium (129.0.2792.89)
  Internet Explorer: 11.0.26100.1882
npmPackages:
  react: ^18.3.1 => 18.3.1
  react-dom: ^18.3.1 => 18.3.1

Current Behavior

The callout that is open after tabbing into one of the points in the LineChart is not automatically closed when navigating focus out of the LineChart in the backwards direction.

video demo:
https://github.com/user-attachments/assets/490b3444-cd15-45d1-9ef0-0178c1a931ac

Expected Behavior

We expect the callout to automatically close when navigating focus out of the LineChart in the backwards direction.

Reproduction

https://stackblitz.com/edit/gcvetp-j4bc13jk?file=src%2fApp.tsx

Steps to reproduce

  1. Open the stackblitz webiste.
  2. Using the keyboard, press the Tab key and focus onto one of the points in the LineChart.
  3. After landing the focus on one of the points, wait for the callout to appear.
  4. After the callout appears then focus out of the LineChart in the backwards direction by pressing Tab + Shift key.
  5. See that the callout which was open in step 3 does not automatically close.

Are you reporting an Accessibility issue?

yes

Suggested severity

Low - Has or doesn't need a workaround

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants