MichaelWest22

@jasontheiler it looks like htmx v2 has resolved this issue so try upgrading. v2 now handles preserved elements on history navigation when I tested it on your example CodeSandbox.

someone reported the same issue in #2790 and we had a discussion there. I put up a small documentation update in #2806 that addresses the same core issue. Your documentation...

yeah the `true` does cause some confusion but I think it is fine as it is. html often has attributes like hidden="true" so htmx copies this and picks the most...

I would go re-read the first couple of paragraphs in the oob-swap-oob documentation which you may have missed while going down the very complex rabbit hole. The most common default...

Hi @coin-au-carre I just had a quick test myself and on both 1.9.12 and 2.0.0 I was able to reproduce that same error when I tried to manually do JSON.stringify(elt)...

```javascript 3916: formData.append(key, JSON.stringify(obj[key]))

Hopefully That callback works well. Just a note that ideally when using htmx you should prefer to use cookies for authentication instead of an authorization header. Normally in htmx the...

yeah interesting workaround! I think it would be great to move the trigger event right to the bottom just before it calls .send so then anyone consuming this event can...

History funciton now re-written in 2.0.5 and it now supports more events and easier override as @manoharank suggested.

The only thing I can see in https://htmx.org/migration-guide-htmx-1/ that could cause an issue is if you have something like hx-on= solving the date picker issue in v1 which needs updating...