kuceb

@psurana0329 this is likely. Do you have a reproducible example you can give?

@psurana0329 this is not a reproducible example. Here's an example of one, which includes the full code needed to reproduce the problem: https://github.com/Bkucera/cypress-plugin-retries/blob/master/cypress/tests/e2e/after-hook-fail.spec.js Note this may take some work on...

> we create a skeleton example @psurana0329 yes, this is exactly what I need, could you provide it? I need more information than just what's in the beforeEach. Like a...

I'll accept a PR, but this plugin doesn't use ally.js in a way where the vuln can be exploited.

@epeli awesome, thanks for the reproducible. I'll take a look

@geebru thanks for this. I believe this was my issue with a11y - if the activeElement isn't tabbable (but is focusable), then you can't get the next element in the...

@geebru this is a bug, right now the command parses all keyboard-tabbable elements and expects the subject to be one of them. It should be updated to only check whether...

the problem is currently the subject is required to be `tabbable`, but it only has to be `focusable`, so `includeOnlyTabbable` won't help. I don't see a clear way to get...

If you could write up a simple failing test that would help get this fixed

@geebru thanks for the reminder - I need to replace a11y with jquery-ui's :tabbable and I believe that will fix the issues Also accepting PRs, happy to help guide on...