Fabian Hiller

Thank you for creating this issue. I will solve the problem as soon as possible. However, I probably won't get to it until the end of the week or next...

I suspect that the problem is that `reset` currently only resets known fields. As you add new fields to the field array, `reset` can't handle them. Calling `reset` twice works...

I will try to solve the problem in the next few days.

I'm sorry that I didn't get back to you on this issue, but other tasks came up. As already written in the other issue, I'm writing my bachelor thesis at...

To give an update from my side. I plan to rewrite Modular Forms but the API should remain almost the same. I will try to solve all these problems. However,...

Thank you very much for the hint. It is possible that my code samples are not up to date. If you need help with Kobalte, I recommend the Kobalte channel...

Since I'm currently writing my bachelor thesis, my mind is on other things at the moment. Unfortunately I can't give you a detailed answer. Please share your further research with...

For Modular Forms only `onInput` is important for capturing the new value.

I'm sorry, due to time constraints I can't take a closer look. If the problem still exists in September, I can check and fix the Kobalte Guide in our docs.

The `type` property specifies which data type is captured, but if the `` or `` element used does not support it, no input is captured at all.