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
Packages Modal - Further Fixes for Modal Trap #13172
Packages Modal - Further Fixes for Modal Trap #13172
Conversation
Hi there @KarlButler1, thank you for this contribution! 👍 While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:
Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution. If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
Hi @KarlButler1 , Thanks for working further on the issue and providing this new fix. I have tested it out and indeed the focus remains solely within the modal window now 👍 I did notice that, when closing the modal by clicking the enter key on the top left "X", the modal closes but focus does not come back on the image which opened the modal anymore. Could you maybe check if you have the same behavior? Cheers! |
Thanks @KarlButler1 for updating quickly again 👍 I tested and this time it all works as expected, so we can merge it (again😅 ) !🎉🎉 I hope you won't mind, but II took the liberty to change the hardcoded color in the .less file by the closest ".less variable color", which was named ui-outline, so I guess it's relatively appropriate 😁 Thanks again for your work on this! Cheers! |
Prerequisites
Related to issue: Fix A & AA accessibility issues throughout Backoffice
If there's an existing issue for this PR then this fixes:
Description
What did you do and why ?
How to test ?