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

:active always returning true since 2.2.7 #99

Closed
SantoJambit opened this issue Oct 18, 2023 · 8 comments
Closed

:active always returning true since 2.2.7 #99

SantoJambit opened this issue Oct 18, 2023 · 8 comments

Comments

@SantoJambit
Copy link

In jsdom/jsdom#3610 I noticed, that the :active selector always returns true. This happened with nwsapi 2.2.7. You already have the fix/revert in the master branch, but not released yet. Any chance of this getting released soon?

Thanks

@dperini
Copy link
Owner

dperini commented Oct 27, 2023

@SantoJambit
will do my best to release 2.2.8 next week since at the moment I am travelling and I don't have my desktop PC with me.

@antoniogamizbadger
Copy link

Looking forward to this! :D Thanks!!

@mxgit1090
Copy link

Looking forward to this for 1 month and more!! Thanks!!

@alopix
Copy link

alopix commented Apr 15, 2024

Any change this is gonna be released soon? Have bee stuck updating jsdom since December due to this bug 😅

@dperini
Copy link
Owner

dperini commented Apr 18, 2024

Forgive my absence but this was not under my control, health and other problems took the precedence over everything else in the last year. However I am ready to start again and try recover your trust by fixing most existing problems.
I surely need everybody help testing and for this reason I opted to use WPT to have a reliable tool and environment to test. Stay tuned !

@alopix
Copy link

alopix commented Apr 19, 2024

Sorry to hear you were unwell @dperini and glad to hear you are better! Health ansd wellbeing definitely come first!

@SantoJambit
Copy link
Author

I've just installed 2.2.9 and it seems to work. Thanks :)

@WesCossick
Copy link

@dperini This issue has regressed in v2.2.10. It was fixed in v2.2.8 and v2.2.9, but has reappeared in v2.2.10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants