Taking a look now, thank you!!

This is starting to make a lot more sense! I'll play around with this more, thank you again!!

yep no prob

https://demo.htmx.org comes to the rescue again, folks

@User Awesome! Because of you example, I was able to get it working in my code. Another question with hx-swap-oob, in the example you have a single target (e.g.

#oob-content

). Can you for example target multiple cards or block contents to be updated? (e.g.

#oob-content1

and

#oob-content2

etc...?

you can add as much out of band content as you want

Wonderful! Thank you!

I am sure you got it already, but I had put together an example using polling and 3 oob targets https://codepen.io/jreviews/pen/bGYmQjx

Thanks @User! Very helpful to see a 3 oob target implementation, thanks! 🙂

Hey, I'm trying to use the HX-Trigger header to make a get request be triggered by multiple sources and I'm having a bit of an issue. So I got the header to contain the HX-Trigger field, and then I marked my requesting element with the custom event from body. This however does not trigger the event it seems. Or at least that's my assumption, I'm not sure how to check if the event is triggered or not. I did however go into HTMX getHeaders method and I see that my breakpoints is not being triggerd in it. Any ideas what I might be getting wrong?

first things first: see if the event is being fired by using `monitorEvents`: https://htmx.org/docs/#debugging

there is no rails htmx channel?

How would I filter parameters out of my form submit event where the input value never changed? I was trying to use Alpine JS to change some

x-data

state when each input fired the

change

event. But then I don't want to use a Javascript

fetch

call, I'd be much happier with an

hx-patch

to match every other call in my frontend.

Is there some quick hyperscript I could use instead?

how come in rails my input data isn't being passed?

<button name="something" value="works" hx-target="#replaceMe", hx-swap="innerHTML" hx-post="/home/value">
  <input hidden name="something" value="something">
  Click Me  
  </span>

when I print out query_parameters and just params I get empty sets

are those both within a form? by default htmx will submit all inputs within an enclosing form. If the button is just off by itself though it won't include it without an explicit

hx-include

parameter.

hx-params

offers filtering, but it sounds like you need to keep some state associated with each input. I would look at using the

htmx:configRequest

event: https://htmx.org/events/#htmx:configRequest and iterating through all the inputs by name to check if they changed and filtering out the parameters that did not. This will require some client side scripting to track initial values as well.

Ah I could put the original value in a

data-

attribute. Cool thank you.

Is it possible to dynamically change the value of a htmx attribute with alpinejs? I'd like something to do something like this:

:hx-trigger="someBooleanValue ? 'click' : 'none'"

which would mean: if someBooleanValue is false then the trigger is disabled. But that doesn't seem to work. I do see that alpinejs changes the value of hx-trigger when the boolean changes, but it seems that htmx disregards any changes made to the attribute.

the trigger is not refreshed by htmx currently. what are you trying to achieve? If you want to disable a request, maybe a trigger filter (which can be dynamic) would work?

Yes that's exactly what I want to achieve: I would like to dynamically disable/enable the request depending on the value of an alpinejs field.

Sorry I forgot to mention that in the example above,

someBooleanValue

is an alpinejs field defined in

x-data

Other question: what's the reason for the HX-Redirect custom header to exist? Why can't I just send a request with htmx (GET/POST/whatever) and have the server respond with 308 redirect?

plugin to make alpine data accessible in event filters, hx-vals etc

Are you saying there is a plugin that makes alpine data accessible in htmx attributes? What's the name of this plugin?

no, i was saying there should be

oh right 👍