-
Notifications
You must be signed in to change notification settings - Fork 400
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: should always have access to slotted elements #939
Conversation
Benchmark resultsBase commit: lwc-engine-benchmark
|
Benchmark resultsBase commit: lwc-engine-benchmark
|
this is ready for review. |
// that element is an slot, then the node is considered slotted | ||
// TODO: add the examples |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing examples.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I tested it locally and wasn't able to find an edge case. I have a hard time to follow enough to review the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm approving this on behalf @ekashida since he creates the tests, and I fixed the code, but he has reviewed my code.
c6a76b7
to
2551033
Compare
Benchmark resultsBase commit: lwc-engine-benchmark
|
Benchmark resultsBase commit: lwc-engine-benchmark
|
* fix(engine): finding slotted elements when querying
Details
Fixes #901 where having a custom element between nested slots causes access issues.
Does this PR introduce a breaking change?