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

fix: [#1472] Fix child combinator matching in nested element #1473

Merged
merged 3 commits into from
Aug 28, 2024

Conversation

ocavue
Copy link
Contributor

@ocavue ocavue commented Jun 27, 2024

Closes #1472

@ocavue ocavue requested a review from capricorn86 as a code owner June 27, 2024 08:28
Copy link
Owner

@capricorn86 capricorn86 left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution @ocavue! 🌟

Sorry that you had to wait for such a long time.

Your fix worked, but I've updated the logic to not use "targetElement" and "currentElement" in matchSelector(), as it felt a bit confusing when I tried to understand the code.

@capricorn86 capricorn86 merged commit 530f535 into capricorn86:master Aug 28, 2024
3 checks passed
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

Successfully merging this pull request may close these issues.

element.matches() returns incorrect result for nested selector
2 participants