Open khiga8 opened 5 months ago
I am going to test bumping axobject-query
to the latest 4.0.0 since that might resolve this bug.
If bumping this package should be done with more care/breaks things, then I may instead suggest a hard-coded update to src/util/isInteractiveElement.js
to immediately resolve this bug.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 99.02%. Comparing base (
882bd4d
) to head (07d3353
).:exclamation: Current head 07d3353 differs from pull request most recent head 89301a8
Please upload reports for the commit 89301a8 to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Good job. Was hoping a fix was one the way for this issue :)
rebased, but it's failing.
@ljharb I see the new failures are related to commit https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/commit/6a048dacf2b98eaa204e2a5a70dc7e3d48d9463a.
Is this needed?
@khiga8 we're stuck on an older version of aria-query and axobject-query, which don't have "summary" in the right place, so i think it is still needed.
@ljharb I'm the blocker here. Would you like permission to publish updates for aria-query and axobject-query? I'd like to remove myself from the dependency chain here so folks are unblocked. I'm flat out with work-work and family lately and I don't have the bandwidth to jump in here.
@jessebeach i'd be more than happy to help maintain those projects! I'd still want you to weigh in on the dequal breaking change stuff tho, which is the blocker for us upgrading.
i'd be more than happy to help maintain those projects
You're a maintainer now. That's one hurdle =D
@jessebeach thanks! do i need npm ownership as well?
@jessebeach thanks! do i need npm ownership as well?
I invited you to both NPM projects. That's 2 hurdles =D
I've rebased this onto main, which has unpinned axobject-query, but aria-query still needs a release for us to be able to unpin it, and presumably at that point this PR will pass tests.
Fixes: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/issues/656
This ensures that
summary
is treated as an interactive element so it doesn't raise a false positive with theno-static-element-interactions
lint rule.