the div is not an input element and contains no other input elements, therefore there is nothing to include.

value

is not a valid div attribute

Ah thanks, so the problem I'm trying to solve is I just need to include something, any value so my backend can recognize it as coming from this page. Can you advise how to do that?

I just want it to do something like, hx-include "xxx" so that in my backend I can say "if this get request has xxx do bla bla bla"

probably, the simplest solution is hx-vals https://htmx.org/attributes/hx-vals you also said

so my backend can recognize it as coming from this page

, sounds awfully like

HX-Current-URL

header https://htmx.org/reference/#request_headers

whats wrong with a query param?

/mypage?from=x

oh but if there is a HX-Current-URL that's better.

oh nvm... you're submitting a form...

😅

Thanks, I don't think I can use hx-values because I can't modify this line of code directly, that's why I wanted it to include a value from a different div, because I can modify that div. But I think HX-Current-URL does sound exactly like what I'm looking for

I can't find an example of how to format this exactly is it something like

hx-headers="HX-Current-URL"

or how to format this?

you don't need to do anything on the front-end, this header should be already attrached

you need to check request headers on the backend, extract the value of this header and implement your page detection logic

ah yes, got it thanks!!!!

Hi! Is there an event that fires when all the scripts inside the HTML that was just swapped by HTMX have finished loading?

I'm not sure if the script tag eval is blocking, but I believe it is. If so, then

htmx:afterSettle

should run after all the script elements are evaluated: https://htmx.org/events/#htmx:afterSettle

The 'HX-Trigger' header doesn't work with my backend server because (I guess) all the headers sent are lower case (so 'hx-trigger') and there is nothing I can do about that. HTTP headers should be case-insensitive. https://stackoverflow.com/questions/5258977/are-http-headers-case-sensitive

I can try to fix that for the next release, I believe we have a reg-ex that might be screwing things up

hx-select-oob doesn't support tbody? That's weird.

html
<div id="content">Content</div>
<table>
    <thead>
        <tr>
            <td>Column</td>
        </tr>
    </thead>
    <tbody id="tbody">
        <tr>
            <td>1</td>
        </tr>
    </tbody>
</table>
<button hx-post="/ex/select-oob" hx-target="#content" hx-select="#content" hx-select-oob="#tbody">Click me</button>

Ajax response:

html
<div id="content">Replaced</div>
<tbody id="tbody">
    <tr>
        <td>2</td>
    </tr>
</tbody>

This replaces #content, but doesn't replace #tbody.

tables are a nightmare to deal with, especially w/ oob

if you are willing to give up IE compatibility, you can use the following setting to make things work:

htmx.config.useTemplateFragments

set this to

true

this will be the default in htmx 2, and we will never speak of tables again inshalla

@mysterious-toddler-20573 thank you so much

@mysterious-toddler-20573 actually it didn't help. I added it in meta tag:

html
<meta name="htmx-config" content='{"useTemplateFragments":true}'>

This works:

html
<button hx-post="/ex/select-oob" hx-target="#tbody" hx-select-
oob="#content">Click me</button>

This doesn't:

html
<button hx-post="/ex/select-oob" hx-target="#content" hx-select="#content" hx-select-oob="#tbody">Click me</button>

Interestingly adding hx-select breaks it as well: This works:

html
<button hx-post="/ex/select-oob" hx-target="#tbody" hx-select-oob="#content">Click me</button>

This doesn't:

html
<button hx-post="/ex/select-oob" hx-target="#tbody" hx-select="#tbody" hx-select-oob="#content">Click me</button>

Thanks, that would be great!

Sorry, your regex is correct. It's another issue: there is something in the web component I use which prevents event bubbling.

To anyone who may have similar problem. The order of tbody in response matters. If it's first element, then the swapping works. Mess...

tables really are a nightmare