Form doesn't reactivate again when receiving itself in Chrome about htmx

[Telroshan]

I understand that you want to figure out the situation here, but there's a first problem even before getting to htmx ; you have an invalid here HTML, as a tbody may only contain tr children, thus not a form.

When you look at the DOM in Chrome's inspector with the HTML you provided, here's how it actually gets parsed:

So all your tr/td containing inputs were moved out of the form itself, thus the form feeling "disabled", but the core issue isn't htmx-related here, it's simply invalid HTML.

In your case, you might want to use the form attribute + get your form either inside one of the td for ex, or outside the table, where it'd be legit to reside

[volysandro]

I noticed this! Weirdly, the form is parsed wrong on both page load and htmx-refresh, the form works on a fresh page load.

And I know it's sacrilegious / not conform..
But I figured chances are high someone splattered paint and encountered the same behaviour, so I was still curious about the root cause:P

[Telroshan]

so I was still curious about the root cause

As said above the very root cause is that it's not valid HTML, thus it's up to your browser to decide how to parse this HTML.
The result here in Chrome is that your form gets disconnected and rendered apart from your <tr> and <td> elements.
Your inputs being no longer inside the form, you have an "input-less" form and "form-less" inputs that have no relationship between each other.
Thus, in your setup, the hx-post is bound to a form that won't ever be triggered anyway as no input/submit button are attached to it.
You can bind these inputs/buttons again to the form using the standard form attribute though.

And I have no idea why the form would work on a fresh page load in the first place given the situation 😆 but don't get me wrong, the anomaly here is the form working sometimes, not the form not working!