Ahhh

that would be the script tag change

we now are much more "normal" rather than eval()'ing in a new context

so global variables are global

😑

but if i declare a const, shouldnt it be scoped to the current tag and not global?

no

it's scoped to the block (usually

{}

)

try wrapping the code in the script in curly braces

OK, it makes the code a bit more convoluted but this works! Eventhandlers are now attached only once. Just out of curiosity: is this something that hyperscript would have made easier?

I think so, in that the event handler would have been embedded directly on the button in question. But hyperscript doesn't support lazy loading of modules like you have, so

Device

would have to be already loaded:

html
<button _='init make Device with "{{ manageddevice.id }}", "{{ manageddevice.androidmanagementname }}
                set element device to it
           on click call device.request_logs()'>
  Get Logs
</button>

Can't say I'm in love with that hyperscript (/cc @User )

you could use

it

instead of giving the device a name. As for imports, shouldn't be too difficult to add to the language

hi, is it possible for

swap

to perform content append to a single

<style>

tag? my endpoints is returning

<style>

tag generated for each html chunk, so would be nice if can have the chunk merged into a a style tag on document head

^ figured out by searching github and linked back to an example,

hx-swap-oob="beforeend"

that is 🙏

How do you actually include multiple fields with

hx-include

as the documentation suggests ([...] CSS query selector of the element or elements [...])? Couldn't find anything searching through this channel either. I tried multiple variations of e.g. this

hx-include="[name='search-input'],[name='clients'],[name='type']"

, but it seems to be ignoring it...

Some sample HTML:

html
<input
  id="search-input"
  name="search-input"
  type="text"
  class="form-control form-control-lg pl-5 rounded"
  placeholder="BBS durchsuchen..."
  hx-trigger="keyup changed delay:500ms"
  hx-get="/search/"
  hx-include="[name='search-input'],[name='clients'],[name='type']"
  hx-headers='{"X-CSRFToken": "{{ csrf_token }}"}'
  hx-target="#search-results"
  hx-indicator="#indicator"
>

hmm, that should work, I'll write a regression for it. In the meantime you can wrap a

<form>

tag around all the inputs and it should include all of them. sorry about that

No worries man; maybe some extra docs on it would be beneficial here too edit: just tried again and it works as expected. When a select has no value, it doesn't add the param. Also I somehow thought that when specifying

hx-include

it wouldn't automatically include the triggering element, which caused the main confusion when "troubleshooting", as I couldn't seem to directly target inclusions.

Hi, I don’t know if this could be considered a bug, but I was expecting that returning a HX-Redirect from the server would make the client execute a client-side redirection, but by respecting the hx-boost. Whatever the status of hx-boost, htmx seems to do a full reload. That’s not super convenient as I try to have a full SPA feeling. I was expecting that the client-side redirection would be caught and boosted the same way as regular anchors and forms. What do you think about that?

Or maybe I should not be using HX-Redirect to fulfill what I am trying to do ? For context, I am just trying to hx-post a specific resource from an anchor and I would like to "redirect" (without a full reload) to the homepage upon success. I could try to swap and return the content of the homepage myself in return of the POST, but just redirecting would be more convenient because involving less server-side logic.

We do try to capture the final URL: https://github.com/bigskysoftware/htmx/blob/2878bd645dfbe999cc03f3e50ba3d2570fb44dd9/src/htmx.js#L2572

If you do a normal 302 redirect

can you try that and see if it work (sorry, this is hard to test)

It actually works (no reload), but the current element on which I triggered the hx-post is swapped by the entire received HTML of the redirected page

And apparently this second htmx request does not send the hx-boosted header

mmm, I bet this is because you are using the

HX-Request

header to filter down what is swapped, and on the redirect that header is lost

That's the nature of http redirects, unfortunately

Can I ask a bit more about your use case here?

Often w/ htmx you can avoid redirects entirely