You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have any of you been able to use history.back() properly with HTMX? I’ve had major issues with it. Because of that, I’ve limited my use of HTMX to cases where I don’t need to push URLs to the browser history.
Here it says you can disable history caching, but when I do that, going back with history.back() swaps the content into the instead of the target I specified.
Also, when navigating back, the data on the page isn’t refreshed. For example, if you add a new record, then call back() to return to the table page, the newly added record isn’t there. We even had to listen to the popstate event in some components to handle this properly.
So, how are you using HTMX to achieve a more SPA-like experience?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Have any of you been able to use history.back() properly with HTMX? I’ve had major issues with it. Because of that, I’ve limited my use of HTMX to cases where I don’t need to push URLs to the browser history.
Here it says you can disable history caching, but when I do that, going back with history.back() swaps the content into the instead of the target I specified.
Also, when navigating back, the data on the page isn’t refreshed. For example, if you add a new record, then call back() to return to the table page, the newly added record isn’t there. We even had to listen to the popstate event in some components to handle this properly.
So, how are you using HTMX to achieve a more SPA-like experience?
Beta Was this translation helpful? Give feedback.
All reactions