TR shouldn't use TBODY as a receiver

[reubenfirmin]

I get that you are trying to force valid html, but that defeats the ability to create html fragments.

Consider the use case:

• I have a table of the first N search results
• I'm using HTMX's reveal to dynamically append additional rows of results (using hx-swap = afterend on the tbody)

Because of the way TR is defined, I cannot dynamically generate a list of TRs, which htmx will take care of appending. (Instead I have to create my own custom element for this, as a workaround, which is sub-par.)

[rromanowski-figure]

I agree it's less than ideal, perhaps a type of "fragment" receiver that any component can be defined under.

Another workaround I see in the wiki is to use a filter if you want to build the necesary parents than define the ones you want to strip out

[dkowis]

I also just ran into this problem. I would like a more flexible method to be able to generate HTML fragments for HTMX specifically.