Putting the div in the fixed the hx-post issue. All fields are now included in the post payload. Wondering which solutions use. My goal is to not returning a non existing car option (say user selected a car chossing car parameter one by one, got some records after filling the form) and then changed the engine and got no records for specified color. My goal is to provide the user with an existing car options via appropriate selects. (we are discussing a much simplified example. In reality there's a different product which has many many more options and available "options"/combinations. That's why must filter out the product options after each selection. Your solution is possible too, but in my opinion harder to code on the backend. Is my solution not the right (but working) or not the way it should be done in htmx?

I know I'm about to 7b myself, but any chance a fix for "linking to an anchor on another page not working well with history API" will be included in the next HTMX update?

absolutely

I am still waiting for a new machine and limping along w/ duct tape and bailing wire

hopefully in a week or so I can be back on htmx dev

@User it seems like https://htmx.org/events/#htmx:afterProcessNode and https://htmx.org/events/#htmx:afterProcessNode say that that

details.elt

is the element that dispatched the event, but it seems like it's the node added to the DOM? are the docs right?

Also, I am trying to modify the response dom, and I think we should be using

htmx:beforeOnLoad

but how do I access the dom node returned from the server? Do I need to parse the

detail.xhr.response

?

That looks like a docs bug

this sounds like you might want an extension that uses the

transformResponse

extension point: https://htmx.org/extensions/#defining

I tried that, but it means I would need to still load the text into through

DomParser.parseFromString

to be able to query the dom yeah? The elt passed into that function is the triggering dom item, not the response dom item.

Right. You would transform the string response. Can you give me an idea of what you are trying to accomplish, maybe I can think of something that would help

Is there any way to request upsert-like swap, i.e. replace a given ID, but if it doesn't exist yet,

afterend

(or whatever) somewhere?

@User We have a some header tags (scripts css) and other tags (scripts/css) that are included in the response html that are wrapped in a templates tag that need to be injected into our DOM outside of the htmx component before we let htmx do it's thing.

We need to insert those scripts/css through our framework's JS so that we can register that they have been injected into the page (we then include them in headers to make sure they don't come back again)

Seems like my question was rhetorical 😉 Thank you for your time and help @User

@User this is the broken code, that isn't achieving what it was trying to do: https://github.com/craftcms/cms/blob/4.0/src/web/assets/htmx/src/htmx.js#L18-L42 The onLoad is too late, as the standard script tags have already been eval'd by htmx

i'm trying to use htmx and hyperscript in wordpress. this is very interesting.

Good evening. I need to trigger two events. When click on row, delete row and Refresh another table (not the one of the row clicked) Click and delete is working ok. I think I need hx-sync, or so I understood but I am not sure and is not working. Can I achieve this without falling back to plain javascript?

🙂 Sorry, very slammed right now. Your solution seems sound to me.

🤔

Would it be possible to include this logic in the base template and then trigger it via an event w/ the

HX-Trigger

headers?

Ah, there is CSS to load too

there are a few different techniques for this: https://htmx.org/examples/update-other-content/

🙂 glad you are finding it useful, hopefully you overcome that initial resistance over time!

do you have a github issue for this? tables are always a nightmare.

@User it seems like

transformResponse

and modifying the html text is the way to go then. We can get it working listening to the

htmx:beforeProcessNode

event but I think that is just because (I guess) eval of scripts does not occur at that point, giving us time to put the script/css tags into the dom - and the elt is the new dom node, not the triggering node (as the docs are wrong) Would you say using

transformResponse

is recommended way though?

to run tests, change into the /test directory and then run

npm install

and start a webserver in that directory. here is python script to do so:

python
import SimpleHTTPServer
import SocketServer
PORT = 8088
Handler = SimpleHTTPServer.SimpleHTTPRequestHandler
httpd = SocketServer.TCPServer(("", PORT), Handler)
print "serving at port", PORT
httpd.serve_forever()

probably but I can also imagine adding a new event in the right spot if you want