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

"Blocked aria-hidden on an element" error upon closing calcite-alert #11494

Open
2 of 6 tasks
MikeTschudi opened this issue Feb 7, 2025 · 0 comments
Open
2 of 6 tasks
Labels
0 - new New issues that need assignment. ArcGIS Solutions Issues logged by ArcGIS Solutions team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. estimate - 1 Very small fix or change (potentially a single line), doesn't require updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - low Issue is non core or affecting less that 10% of people using the library

Comments

@MikeTschudi
Copy link
Member

Check existing issues

Actual Behavior

Error message appears in debugger console when alert is closed:

Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: button
Ancestor with aria-hidden:
Image

Expected Behavior

No error message

Reproduction Sample

CodePen in doc page https://developers.arcgis.com/calcite-design-system/components/alert

Reproduction Steps

  1. Go to alert doc page https://developers.arcgis.com/calcite-design-system/components/alert
  2. Open "Edit sample on CodePen"
  3. Open the debugger
  4. Close the alert using the close button

What's weird is that if I change the Calcite version, the problem is usually not repeatable, including if I go back to version 2.13.2. (I was trying to answer the regression? question.)

Reproduction Version

2.13.2

Relevant Info

Windows 11 Enterprise; Chrome 132

Regression?

No response

Priority impact

impact - p3 - not time sensitive

Impact

It does not affect our team at this time.

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/calcite-ui-icons
  • @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Solutions

@MikeTschudi MikeTschudi added 0 - new New issues that need assignment. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. needs triage Planning workflow - pending design/dev review. labels Feb 7, 2025
@github-actions github-actions bot added ArcGIS Solutions Issues logged by ArcGIS Solutions team members. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive labels Feb 7, 2025
@DitwanP DitwanP added p - low Issue is non core or affecting less that 10% of people using the library estimate - 1 Very small fix or change (potentially a single line), doesn't require updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed needs triage Planning workflow - pending design/dev review. labels Feb 18, 2025
@DitwanP DitwanP removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - new New issues that need assignment. ArcGIS Solutions Issues logged by ArcGIS Solutions team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. estimate - 1 Very small fix or change (potentially a single line), doesn't require updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - low Issue is non core or affecting less that 10% of people using the library
Projects
None yet
Development

No branches or pull requests

2 participants