Vincent

We indeed switched to FormData internally for htmx 2, so you get the standard event fired when building one over a form element. We also introduced a FormData proxy object...

Hey, do you see it still happening in htmx 1.9.11 ?

Htmx is designed for communication with the server after all, for pure client side logic such as your usecase here, you may use [_hyperscript](https://hyperscript.org/) (also by 1cg) or simply use...

I personnally do exactly what you described, i.e. adding the ID of the item in the event name > This workaround is not ideal, and the data field of the...

Hey, I think that's something you will have to tweak in your component. What does it do exactly? Because by default, non-standard elements won't be included in a form payload,...

Oh I see, so it works through `FormData`, I didn't know that there was support for that now! #1686 and #1323 seem related, htmx does not use `FormData` internally for...

Please note that a `FormData` rework would, if accepted, only occur in htmx 2 (breaking release) as it's not fully IE11 compatible, and htmx 1 strives for IE11 compatibility

Yeah as they have many differences in their behavior, I don't think it'd be reasonable to support & maintain both in the same codebase Htmx 2 is coming soon and...

We don't have a roadmap I'm afraid About "soon": you can find the latest _(afaik)_ official mention of htmx 2 here for the 1.9.10 release announcement https://x.com/htmx_org/status/1738012396470370611 > this is...

Hey, we switched to FormData internally for htmx 2, which should now correctly handle webcomponents (see test added in 01b292ada48f31276642b587eb67128367349701). We also introduced a FormData proxy object for retro-compatibility reasons,...