Is there conditions in which Flickity removes child elements ?

**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!

Start with the linked CodePen test case and compare the custom model-viewer element with the dummy custom element. Trace when Flickity initializes and changes its child elements, then determine whether the element is removed by Flickity or by the custom element itself. Done means documenting a reproducible cause and a confirmed fix or compatibility limitation.

Written by the indexing model from the issue text.