Collapsing tree component inside a form crashes and reloads the page about patternfly-yew HOT 10 CLOSED

Minimal example here: https://github.com/aDogCalledSpot/patternfly-test

from patternfly-yew.

Can confirm that it works 😁

Thank you so much for the quick help! I really appreciate this repository and the work you're putting into it!

from patternfly-yew.

I think having a tree inside a form should just work. On the other side, the tree stuff is pretty new and experimental.

What sounds a bit weird to me is the "reloading" part. If you're using trunk serve, that might trigger a reload because of a code change. And trunk might compile a few times too often, which might lead to a few reloads after a change. If that's the case, then simply some patience is requires, or the patched trunk version which fixes this.

A crash can indeed happen, but that would be a panic, and should be visible in the browser's console. If that's the case, then it would be good to have this information, because that would tell us what is wrong.

from patternfly-yew.

This also has me confused. I don't see anything from trunk, the developer console in my browser doesn't output anything and trunk doesn't recompile at all.

Here's a brief video for reference. The same thing happens in the example I posted above.

I'm running in this in Firefox.

from patternfly-yew.

Hm, this looks interesting indeed. It feels like the click on the toggle navigates away from the page, causing the reload. So maybe there is some event bubbling up.

It would be great if you could share a reproducer. That might help.

from patternfly-yew.

Minimal example here: https://github.com/aDogCalledSpot/patternfly-test

404 😉

from patternfly-yew.

Sorry, visibility of the project has been updated.

from patternfly-yew.

So it looks like it is reloading:

Enabling the persistent console option shows it.

from patternfly-yew.

Ok, found it! the button of the toggle must have the type attribute set to button, otherwise it is submit, which triggers a form submission. Which also explains the behavior you saw and why we didn't encounter it so far :)

from patternfly-yew.

If you update the git rev, you should have a fix! And thanks for the reproducer, this really helped!

from patternfly-yew.