Open commit-master opened 8 months ago
Do you see any reasons why your library would remove our element from the DOM ?
Flickity creates two elements .flickity-viewport
and .flickity-slider
, then moves cell elements into those parents. What may be happening is that Flickity's DOM manipulation is messing with how omi-360-viewer works.
One solution may be to initialize Flickity first, then initialize omi-360-viewer afterward, using JS to initialize both so you can control the order.
Test case: https://codepen.io/commit-master/pen/poGLZWW
We are working with customers that use Flickity. Somehow the carousel is not compatible with our Custom Html Element (omi-360-viewer). I've been searching everywhere and I cannot seem to find a reason why in that case the element is removed.
It's specific to our custom element since trying with a dummy one works.
Here is what our element returns as HTML:
Do you see any reasons why your library would remove our element from the DOM ?
We've been working with others carousels library and we don't have the issue. We'd love for our mutual users to be able to use it.
Thanks!