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

Test script: cycle tab #2

Merged
merged 2 commits into from
May 27, 2022
Merged

Test script: cycle tab #2

merged 2 commits into from
May 27, 2022

Conversation

gabalafou
Copy link
Collaborator

@gabalafou gabalafou commented May 14, 2022

No description provided.

@gabalafou
Copy link
Collaborator Author

gabalafou commented May 14, 2022

Here are some screenshots of how the test failures look in Playwright with this additional test.

image

image

If you watch the video that Playwright produces, you can actually see Playwright tabbing across the JupyterLab UI wherever it lands on elements that have visible focus, and then it just tabs off to nowhere.

@trallard
Copy link
Member

@trallard check in GitPod

Copy link
Member

@trallard trallard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - managed to run this on Gitpod and all seems to be working ok 👍🏽

is there any more work needed atm?

@gabalafou
Copy link
Collaborator Author

is there any more work needed atm?

Nope. All good to merge. I simply forgot to take the PR out of draft mode earlier.

@gabalafou gabalafou merged commit a26df3c into master May 27, 2022
@gabalafou gabalafou deleted the a11y-test-no-keyboard-trap branch May 27, 2022 15:26
@gabalafou
Copy link
Collaborator Author

gabalafou commented May 27, 2022

I just merged this into the main branch. So next step is... use the same branch of this PR (a11y-test-no-keyboard-trap) to open a new pull request against jupyter/accessibility?

@trallard
Copy link
Member

Pull Request from this repo master into jupyter/accessibility master to avoid having diverging histories 😉

@gabalafou
Copy link
Collaborator Author

@trallard like this? jupyter#92

@trallard
Copy link
Member

Yes - we need to merge #5 before merging to avoid issues with the GH actions

@trallard
Copy link
Member

Now that #5 is merged we can mark your PR as ready 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done 💪🏾
Development

Successfully merging this pull request may close these issues.

2 participants