-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 incorrect value of [aria-expanded]
on menubuttons
#5255
Conversation
Rebased on the newest master. |
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.
@Comandeer I left one significant inline comment. There are two ways to choose there (or you can see even more?). I believe you can choose the right one based on your a11y knowledge. However, if I'm incorrect at some point - please let me know :p So we can establish the approach together 👍
I've completely rewritten the solution. I've moved the logic responsible for setting the |
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 job!
What is the purpose of this pull request?
Bug fix
Does your PR contain necessary tests?
All patches that change the editor code must include tests. You can always read more
on PR testing,
how to set the testing environment and
how to create tests
in the official CKEditor documentation.
This PR contains
Did you follow the CKEditor 4 code style guide?
Your code should follow the guidelines from the CKEditor 4 code style guide which helps keep the entire codebase consistent.
What is the proposed changelog entry for this pull request?
What changes did you make?
As explained in #5144 (comment) I had to find another way to detect if the menu is open. Fortunately, this information is available as an internal property of the button,
button._.on
.I was thinking about exposing this property as a public one but finally decided not to do that. This decision really simplified the solution but at the same time – made it a little bit dirty (as the internal property is now used directly inside the
button
plugin)Which issues does your PR resolve?
Closes #5144.