-
Notifications
You must be signed in to change notification settings - Fork 77
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
fix(modal): fall back to modal id for dialog aria-labelledby
attribute
#1403
Conversation
Thank you, 🤖 Clarity Release Bot |
aria-labelledby
attribute
7d8c34b
to
104cfa3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch
…ute (#1403) ## What is the current behavior? If you set `[clrModalLabelledById]` to an empty string, the `aria-labelledby` attribute of the modal dialog element is set to an empty value. This behavior can be seen in the modal stories since the input is defaulted to an empty string. We can't default it to the modal id because that is not known until the component is instantiated. Issue Number: CDE-2050 ## What is the new behavior? If you set `[clrModalLabelledById]` to an empty string, the `aria-labelledby` attribute of the modal dialog element is set to the modal id. (cherry picked from commit 6493dc3)
…ute (#1403) If you set `[clrModalLabelledById]` to an empty string, the `aria-labelledby` attribute of the modal dialog element is set to an empty value. This behavior can be seen in the modal stories since the input is defaulted to an empty string. We can't default it to the modal id because that is not known until the component is instantiated. Issue Number: CDE-2050 If you set `[clrModalLabelledById]` to an empty string, the `aria-labelledby` attribute of the modal dialog element is set to the modal id. (cherry picked from commit 6493dc3)
…ute (backport to 16.x) (#1407) Backport 6493dc3 from #1403. <br> ## PR Checklist - [x] Tests for the changes have been added (for bug fixes / features) - [N/A] Docs have been added / updated (for bug fixes / features) - [N/A] If applicable, have a visual design approval ## PR Type Bugfix ## What is the current behavior? If you set `[clrModalLabelledById]` to an empty string, the `aria-labelledby` attribute of the modal dialog element is set to an empty value. This behavior can be seen in the modal stories since the input is defaulted to an empty string. We can't default it to the modal id because that is not known until the component is instantiated. Issue Number: CDE-2050 ## What is the new behavior? If you set `[clrModalLabelledById]` to an empty string, the `aria-labelledby` attribute of the modal dialog element is set to the modal id. ## Does this PR introduce a breaking change? No. Co-authored-by: Kevin Buhmann <kbuhmann@vmware.com>
🎉 This PR is included in version 17.2.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary. |
PR Checklist
PR Type
Bugfix
What is the current behavior?
If you set
[clrModalLabelledById]
to an empty string, thearia-labelledby
attribute of the modal dialog element is set to an empty value.This behavior can be seen in the modal stories since the input is defaulted to an empty string. We can't default it to the modal id because that is not known until the component is instantiated.
Issue Number: CDE-2050
What is the new behavior?
If you set
[clrModalLabelledById]
to an empty string, thearia-labelledby
attribute of the modal dialog element is set to the modal id.Does this PR introduce a breaking change?
No.