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
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
When an application uses routing, the application has its CDK Dialog instance (A), and the route's component has its own CDK Dialog instance (B), which has A as its parent.
When B opens a component in an overlay, it sets the aria-hidden attributes.
When the application provides a set of shared dialog components and a service to open them, they are opened from A, and aria-hidden attributes are not set because they are already present. (see Dialog._hideNonDialogContentFromAssistiveTechnology).
When B removes the last dialog (see Dialog._removeOpenDialog) while its parent (A) has dialogs open, the aria-hidden attributes are not removed.
This means that because the parent CDK dialog (A) doesn't know that the child dialog had any attributes set, the aria-hidden attributes are never removed again, and the application becomes inaccessible to assistive technologies.
Is this a regression?
The previous version in which this bug was not present was
No response
Description
When an application uses routing, the application has its CDK
Dialog
instance (A), and the route's component has its own CDKDialog
instance (B), which has A as its parent.When B opens a component in an overlay, it sets the aria-hidden attributes.
When the application provides a set of shared dialog components and a service to open them, they are opened from A, and aria-hidden attributes are not set because they are already present. (see Dialog._hideNonDialogContentFromAssistiveTechnology).
When B removes the last dialog (see Dialog._removeOpenDialog) while its parent (A) has dialogs open, the aria-hidden attributes are not removed.
This means that because the parent CDK dialog (A) doesn't know that the child dialog had any attributes set, the aria-hidden attributes are never removed again, and the application becomes inaccessible to assistive technologies.
Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-starter-aa1qpb
Steps to reproduce:
Expected Behavior
All aria-hidden attributes set by dialogs are removed again.
Actual Behavior
The aria-hidden attributes set by CDK
Dialog
B remain.Environment
The text was updated successfully, but these errors were encountered: