interesting!

I have a popup menu which contains an hx-post action. When the action is triggered, I'd like to remove the menu from the DOM (hiding the menu doesn't work with history cache). However it appears that removing the trigger element from the DOM prevents any HX-Trigger events in the response from being handled. Is there a workaround for this?

The response returns a 204

we should still trigger the event, regardless of return code: https://github.com/bigskysoftware/htmx/blob/6d85d1ae5b8edd20745fcbd17385dcf8ed0b3d3d/src/htmx.js#L2424

Yes - it looks like the event won't be triggered if the element is no longer in the DOM.

this should happen before any content is swapped though

so the element should still be in the DOM, unless it is being removed some other way

sure, but if I'm removing the menu in JS, not htmx

Ah, OK

I think the solution is have the endpoint return an empty 200 targeting the menu

How are you registering the even handler?

are you listening on the body?

my original idea was having an HX-Trigger from the response - say "close-menu" - and have an event to remove the menu from the DOM on that event (listening on window/document). While this works, any other HX-Trigger events in the response aren't triggered, i.e. once that trigger element is removed.

hello

i have qustion: how can i connect a simple python socket app with htmlx web-socket (hx-ws)

I’m going to use it in production but this thing is awesome for prototyping

nothing special on the htmx side

yep, you can move really fast once you get the hang of it!

feedback welcome 👆

I was a fan of the path dependencies feature of Intercooler, because we use clean, hierarchical urls it worked really well. I even contributed to the htmx dependencies plugin to add the api “refresh” method, because it’s still pretty useful imho, spooky action at a distance notwithstanding 😁

I’m not sure we tell you often enough how great a thing you’ve done with htmx, @mysterious-toddler-20573 & co! Here’s one way people can really show their appreciation and support: https://twitter.com/jvosloo/status/1436384677850402819?s=21

🙂 thank you sir and thanks to everyone who has contributed, including @User @User @User and many others I'm sure I'm forgetting. I am starting to think about how we can make htmx an actual money making business w/ consulting, etc. Obviously it will always be free and open source, but it would be awesome to make a living doing this stuff at some point 🙂 🍺

evened out a bit now, still strongly in the "pull out" camp

It should be. You’ve put in so much, and given so much to the community. Think of how much more it could be if you could dedicate yourself to it full time.

iam trying to get service workers working to intercept and cache requests from htmx with no success. Does anyone have pointers?

i think you are on the outer edge of functionality

I’m just shooting in the dark, but try this: write an event handler that looks at

htmx:afterRequest

then pass the data you need to the service worker from there.

I agree with DHH that this video is the best introduction I’ve seen to Hotwire. I also think most of the 1st half of the video might as well have been describing htmx (barring the ‘merge the head and replace the whole body’ bit. Progressive enhancement is cool, but html fragments ftw). It’s towards the end where the powerful, low-level flexibility and simplicity of htmx + hyperscript/alpine.js begins to shine, ‘cause my eyes start glazing over when I hear about turbo frames and Stimulus controllers 😅. Oh… and did I mention that htmx works with... any backend? I’m still delighted that Hotwire exists, as it promotes the same philosophy as htmx and others who believe html over the wire is just fine. It really is a great video though and I wish someone would make a similar explainer video for htmx. https://twitter.com/dhh/status/1436603249776287745?s=21