htmx

the history API is so crazy, I can understand it for about 30 seconds a week, so I have to code fast, and then it's gone

if it doesn't work I'll try to sit down w/ it tomorrow.  Today is the day americans endanger their lives and the lives of everone around them with explosives because we didn't want to pay taxes

Did you perhaps miss the state in this line?
```
if(htmx.config.historyEnabled) history.replaceState({}, getDocument().title, window.location.href);
```

https://github.com/bigskysoftware/htmx/blob/947a4470de7cca21479ed6f9a761d4bf56e451d9/www/js/htmx.js#L1069

With that (correctly) in place it is working in my manual tests.

OK, pushed up w/ that fix in /src properly

thank you for pointing that out, sorry for the trouble

Perfect, thanks for jumping on this so quickly <@!725789255590215732>! 
Back to comforting the cats and dogs at home 🎆

<@!725789255590215732> Could it be that this addition has broken the back button from using local storage?

Never mind, was testing old code, dammit.

> <@!147049946456129537> Probably wise to require a specific version of htmx at this early stage, e.g. https://unpkg.com/htmx.org@0.0.7
<@!456923424065978381> Yup, I'm all ok with it. It just was a moment when I was reading the documentation, and after ordinary page refresh suddenly something changed 😛 And I even couldn't figure out what exactly 😛

I think by the end of the month I'll have a 0.1.0 released and at that point the breaking changes will slow down (I hope)

still wondering about the colon-separated event namespace

I will cut a new release today w/ the fixes

<@!725789255590215732>   Great! I'm also wondering about `target.scrollTop = 0;`

Doesn't seem to be working in my initial tests.

https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollTop

0 would seem to be the correct value to have it scroll to the top

one confusing thing is that this is on the target element only, so the target needs to be scrollable, is that the issue?