htmx

my hack for making the `htmx:confirm` event act like it is blocking: https://github.com/bigskysoftware/htmx/blob/a3c414dcee94fd03... basically, redesign the arguments for a function such that I can call it again at a given spot with one parameter changed and, to a first order approximation, it acts as if the function is resumable. I've used this trick in a few places now, just recently in idiomorph to allow head elements to load before the rest of the content is morphed: https://github.com/bigskysoftware/idiomorph/blob/e6dfc189fa3...

as usual, htmx: https://github.com/bigskysoftware/htmx working on an extension to do head tag merging: https://dev.htmx.org/extensions/head-support/

Intersting. How did you work around the issue that HTMX takes snapshots of the altered DOM (by Alpinejs) for history navigation [0]? This is the biggest issue holding me back from using the two together. [0] https://github.com/bigskysoftware/htmx/issues/1015

> 2) If there's a form input at each step, the server needs to store that info and be aware that the user has an incomplete checkout. Now the user is at step=2 and presses the back button, or clicks on the step=1 link. In that case, the server should know the information stored in the point no. 2 above, and return an HTML form with the data pre-filled based on the last state. The problem is that when you press back button in the browser, it doesn't make another request to the server. It reloads the page from browser memory. A link back can be made to work, but that's not what I was speaking to. I tested the most trivial case, when you return a response, and push navigate to next step, then press browser back button, form state is not retained. Both chrome and firefox do not restore the form state on navigation back after a url push naviga