got it

you could also do this w/ an event filter, but I think this is cleaner and more async friendly

btw: do you know some IDE pycharm plugins to read format the hyperscript and htmx

nope, not yet

but please harass JetBrains!

done

HX-Boosted Anchor Targets and History · ...

Is there a bigfunctionaly difference between doing something like

hx-target="#target" hx-swap="beforeend"

or just returning

hx-swap-oob="beforeend#target

to mee the former makes it clearer as to how the app functions, while the latter hides some of that since it's not co-located to where it's going to end up

I would prefer the former

but sometimes if you need to update multiple things, the latter is necessary

i tried to be pragmatic and give people a few escape hatches when necessary

That makes sense

From another viewpoint it would be simpler if the returned elements always specified their swap/target and their child elements were applied, like oob elements are. It is a little confusing to have a response that has several form fields at the top level that are applied using the non-oob approach, plus some oob container elements at the top level, which is common for me at least -- there is an inconsistency there. I'm not complaining, just a comment in case simplifications were being considered for 2.0. In general I think the htmx approach is fantastic and I'm very happy using it.

Also my preference is to have one way of doing things instead of two.

I tend to agree, if not we have to wait until so many htmx users have done it so many ways that we gravitate to commonly accepted idioms for common scenarios

Which also is fine, because that tends to have more people thinking about the problems and offloads the work from the library dev

I'll try using all oob results to see if that is really simpler.

wasn't Paul Everitt a big fan of htmx?

I tried it. It is more consistent to use oob for all the responses, but I'm not sure it's simpler. You need an additional id (if not already needed) that goes in the parent element as well as the oob response. (You also have to add

hx-swap="none"

in the parent element, but if everything was done oob then this wouldn't be needed.)

found the answer myself. Time to keep pestering JetbBains and Paul 😄 https://twitter.com/paulweveritt/status/1499079390596153347

I tried it It is more consistent to use

Foudn odd behavior, when I click a button that has an hx-get, and the response does an hx-swap-oob to another target, the text in the button itself disappears after the response does the swap

had to use hx-swap="none" in that case on the button.

I have similar issue. i show confirm dialog but on Yes I show OTP modal and what happens is as if that Yes click causes confirmed event while I want Yes to instead lead to OTP modal and on its success I need to trigger both closeModal and confirmed. can you guide ? https://github.com/bigskysoftware/htmx/discussions/951 row_ro.html has Delete action leading to Confirm Dialog. Earlier I did not have OTP dialog so it was working fine but with addition of OTP dialog I am facing issue that confirmation Yes causes UI row to be deleted from front end. backend its not deleted since it will delete on OTP match. tried htmx.logAll() and monitorEvents on gamelist table but could not still figure out.

Out of curiosity, why are those ignored?

are you returning only the OOB swap?

You only want to include the value of the clicked button

we try our best, but it is (or was, haven't looked at the apis in a while) hard to get the source of the element that caused the submit: https://github.com/bigskysoftware/htmx/blob/299a9baa1df31bcee78f52677c4444095b5b3db2/src/htmx.js#L1676

yes, only the oob swap component is returned, I had to put hx-swap="none" to get it to not swap the button contents. I also noticed that when I do an oob swap with something like

beforeend:#someID

in some cases the child elements of that one are put in that location, not the entire outerhtml