Daniel Eggert

Does one of you have an idea for fixing the test case?

:thumbsup:

Hi, thanks a lot for your effort. I just tested the feature. The expand event is fired consistently when an item is expanded, but the collapse event on the other...

> For the Collapse and Expand event is registered to MaterialCollapsible, so we might want to step down to it's Collapsible Items for the required usecase. Sounds like the solution...

Looks appropriate. Do you need support for the implementation or will it suffice if I test the result?

Is it okay to use an existing wrapper for the MutationObserver (like [gwtquery/gwtquery-observe-plugin](https://github.com/gwtquery/gwtquery-observe-plugin)) or do you prefer your own wrapper

Thanks for the hint! I just tested the elemental2.dom.MutationObserver. In order to pass the CollapsibleItem as the observed Node I had to cast it like this: `observer.observe(Js.cast(collapsibleItem.$this().asElement()))`. Is there a...

ok, so i will prepare a pull request within the next couple of days.

@srmnitc The publication looks interesting, but I have no time available at the moment, sorry.

I have the very same issue. @markogresak did changing the update interval fix it?