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
[BUG] DOMException: The selector ":not" is not valid. when using .not.toMatch #1352
Comments
…elector-not-is-not-valid-when-using-nottomatch fix: [#1352] Ignores invalid selectors when parsing CSS in Window.get…
Thank you for reporting @SalahAdDin! 🙂 The error throws seem to be that You can read more about the release here: |
…cted using the "new" keyword rendered as <null>
It sounds good, but:
@capricorn86 Should I open a new issue? |
…here without argument was not handled correctly
…elector-not-is-not-valid-when-using-nottomatch-2 fix: [#1352] Fixes problem when the error for the selector :is and :w…
@SalahAdDin this problem should also be fixed now 🙂 https://github.com/capricorn86/happy-dom/releases/tag/v14.3.8 |
And yeah, finally it is fixed. Tesekkur ederim |
Describe the bug
After updating the
happy-dom
version to the latest one, we are getting the following error:It happens for the following code:
Only this file has that matcher:
And the component does not include any
:not
pseudo-element:We updated from 13 to 14 version:
To Reproduce
Steps to reproduce the behavior:
not.toMatch
query on any element.happy-dom
version.Expected behavior
It should not give any issue.
Screenshots
If applicable, add screenshots to help explain your problem.
Device:
Additional context
We checked it with all versions from 14 to 14.3.2 and it seems it is broken from the 14.2.0 where some pseudo selectors where introduced.
There is also a typo error in
SelectorItem.matchPsuedo
.The text was updated successfully, but these errors were encountered: