fix(core): set isElement on swiper-containers only #6870
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Merged, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @nolimits4web!
I think you introduced a subtle bug with the swiper web component.
In the core you expect the swiper to be a swiper webcomponent whenever it's parentNode has a host, but you forget that the swiper might be a direct child to another (non-swiper) webcomponent.
When that is the case (which happened to me), you assign this other web-component as "slidesEl" to the swiper object.
I noticed that when using the manipulation module's "appendChild" method which now assigned new slides as children to my own web-component.
I suggest to add another condition to the isElement check (see commit).