@mysterious-toddler-20573 Stepping back a bit, I'd like to validate my understanding of the htmx philosophy. Basically, like traditional html, we aim to make stateless pages, where the URL defines the content of the page. But we are also pragmatic, and are ok if the state of our page drifts a little as a result of htmx swap interactions (eg, the editable row we just discussed not having a history URL associated with it). We want to use this kind of thing judiciously, and want to avoid pages that are many "steps" away from their starting state. Also, the "state" is the DOM in the htmx model. So even when we've altered our original page with no URL changes, this new state is never stored as JS variables, but is implicit in the mutated DOM that has been accomplished via htmx swaps. Have I got it basically right? If not, what would you correct?

that sounds about right. I'd say that the DOM may have some local UI state not reflected in the traditional stateless URL model (e.g. a modal up) for UX reasons, but that should be minimized and ideally we want to ensure all system state is always reflected in stateless URLs

but I'm also pragmatic about it, sometimes you have to do what you have to do. I'm not going to judge.

Thanks. I'm not worried about judgment 🙂 but I find that using systems in accordance with their design principles is usually the best path, so having access to the designer and understanding how they see things is invaluable.

Is there some way to invoke

hx-boost

behavior from the server-side? I'd like to serve the "form w/errors" partial by default and redirect to the "items list" page on success -- but I don't want to do a full refresh -- I want to stay in happy hx-boosted-land. 🙂

This involved hyperscript and htmx, so I'm asking here first. I created a general function to handle htmx requests. Something like this:

<body _="on htmx:beforeRequest
                add .main--hidden to .main 
                wait 150ms
                then settle then go to the top of the body instantly
            end">

There a few other things but the htmx:beforeRequest is the key part. Now, I have another element in my project, that needs to have its own logic for the beforeRequest. So the question is how to ignore the one defined in the body tag? If I define a new one like this:

<form _="on htmx:beforeRequest ...etc.">

would it take precedence over the one defined on the body? Or should i do it differently? Thank you so much!

you probably want to use

halt

in that event handler to prevent bubbling, which will prevent that event from hitting the handler on the body: https://hyperscript.org/commands/halt/

Excellent. Thank you so much! Didn't know about the

halt

command! I'll give it a try now.

https://github.com/bigskysoftware/htmx/discussions/867 The discussions on GitHub is not very active... I posted an example proposition that is waiting for comments since 10 days. (not a criticism...)

we have been struggling with how to best manage all the different possible forums available: stack overflow, github discussions, reddit, twitter, here

I keep ending up back here, but then stuff gets lost forever

maybe @User will save us

I’m coding as fast as I can (which is not that fast, honestly) but it’s going to be a while before there’s anything remotely as polished as Discord 😢

I think it would be good to redirect people where it is the most active... Don't know how. Isn't it possible to send notice to Discord when a new discussion on GitHub is created?

please investigate!

https://dev.to/inezabonte/how-to-get-github-notifications-on-your-discord-server-2j9o It seems easy to setup...

This is a bit delayed - but, what I ended up doing is combining HX-Retarget (for where the new content needs to go) and HX-Push (to send a new URL) to simulate a redirection. Both are headers you'd send from the server in the response.

Thanks Daniel -- that's what I've ended up doing too. It would be great if there were a header:

HX-Boost: true

– it's such a killer feature. Seems a shame not to be able to invoke from the server.

Sadly, the reason it doesn't is due to the architecture of the web. Once a POST has been issued, the browser is handling the communication, not an htmx-controlled XHR. Once a non-boosted request has been issued, the browser needs to receive a full page in response. :/

Hmmm... My understanding was that with

hx-boost

, you DO receive a full page but then extract only the

body

chunk of the DOM to swap in. Maybe I'm missing something.

Close. The biggest difference between a regular click and a boosted click is that htmx intercepts that click and sends it via JavaScript (XHR =

XMLHTTPRequest

); since it's then technically a dynamic interaction on the page, the page itself doesn't change. Without htmx, the browser initiates the navigation by requesting the URL from the remote server. As far as the response, you're correct that htmx will swap in the

body

to the target element in the existing page. This could be a completely full page's worth of content swap, but it doesn't have to be. Take the inline edit example on their site - the request to edit returns a form that replaces the list item entry, and once the item is submitted, the text to display that item entry is returned. When you have control over the server side, you can send different responses at the same endpoints, based on whether the request is from htmx or not; that's what I do for my "page" templates (one is full page, one is just title and body).

Makes sense. Thank you for the thorough explanation. 🙂

Hello, how can i use hx-trigger if values= null

Can you explain a bit more?

oldie but a goodie

I think I asked this before, but: is there any way to specify multiple oob targets? e.g. something like

outerHTML:#view-xyz, beforeend:#clist

that would replace

#view-xyz

, but if that doesn't exist, append to

#clist

, etc?

tl;dr, I want something like DOM upsert 😛

Check this answer out. I think it will help. Basically, yes, you can specify multiple oob targets that target different parts of the page.