Hi all, I've been following htmx for a while and recently convinced my company to give it a try for a wizard style flow. I've managed to implement it much more easily than it would've been with react! One thing that isn't working as expected though is hitting the back button. Specifically: the first step in the wizard has a form with input fields. Filling them, hitting next submits the values correctly. Hitting the browser back button afterwards shows the form again, but with empty fields. Here's a jsfiddle to demostrate the issue: https://jsfiddle.net/w90e8gyr/4/

any ideas what could be happening or if this is expected? I thought htmx would snapshot the html before swapping the new html, does that not include the input values?

Strange that it works going back to the form at all since its not pushing url

Try adding hx-push-url="true" to the form?

daily reminder that using the word "hydration" with or without a preceding "partial" or "resumable" modifier is an instaban on this IRC node

you could just add a tag "hx-hydrate" that does nothing? and the documentation could deal with it, like it's obvious what it does.

\> hx-hydrate I'll allow it

"set True to activate hydration, set False to stay in 20th century."

(I have no clue at all what this even is I have to admit)

it would be hysterical to add an

hx-h**drate

attribute that does nothing

sorry. It got the better of me 😳

possible values:

"partial"
  "resume"
  "transfigure"
  "false"
  "wat"

resident hydration understander here, this is like asking "will YAML support async-await?"

like the feature only makes sense if you have client-side code

this is dangeround ground to tread, however, as I run the risk of understanding the dread word

eXtensible Moist Language

I mean isn't hydration just hx-trigger="load" anyways?

Don't ban me

> The concept of hydration doesn't realy make sense for htmx, it's a solution to a problem that only frontend frameworks have. Qwik does it by encoding frontend state in the HTML but in htmx apps, there is no frontend state other than what's already in the HTML. You change this state by making server requests, just as you would in a no-JS app by clicking links and submitting forms. State management is handled by the browser. You also get time-travel debugging, in the form of the browser back and forward buttons. (See this essay on for more info on this concept). > > The closest thing to hydration we have is that when htmx swaps in a new fragment from the server, that fragment can also have HTMX attributes and htmx will attach the necessary event listeners (and websocket connections, if you're into that) to the elements. And since you're not repeating any computation done on the server, I'd consider this similar enough to resumable hydration. -- me, in reply to that https://www.reddit.com/r/htmx/comments/uo8jva/comment/i9h0qxd/?utm_source=reddit&utm_medium=web2x&context=3

yes more of my face everywhere, this is good

guys I'm really thirsty what should I do

htmx - we put the Hydra in hydrate

I have lately been feeling bad I only use Django/HTMX at my job and not something like react/vue simply cuz its too much overengineering for what I need, but then this makes me feel better

Current web developer paradigm makes knowledge of react a need almost, bit sad

lol I looked at reactjs vs htmx jobs on indeed today