https://htmx.org logo
Powered by
# htmx-general
  • p
    and finally, just call htmx.ajax manually do fetch the explicit URL
  • p
    (by default I think it targets body?)
  • p
    There's some jagged edges here and there (see above) but alpine & htmx are a very good combination
  • m
    Keep notes so we can make 1.4 sing
  • p
    seeing some odd issue around modal behavior: so I have a modal element at the bottom of the page. Clicking on a button does an hx-get with target on the modal element. Works fine
  • p
    however if I hit the backbutton, the modal action is somehow re-triggered, and the modal appears twice (and if I keep hitting back the same action is re-triggered)
  • p
    is htmx doing something weird with the history cache?
  • p
    hitting a back button shouldn't do anything to trigger an hx-get action
  • p
    (again I have hx-boost on by default, I suspect this is causing a number of bugs)
  • s
    not sure if solves your problem but i switched entirely to https://www.npmjs.com/package/dialog-polyfill over modals.
  • p
    It's not just modals where I'm seeing this
  • p
    Basically client state is being restored through back button
  • s
    I just disable history cache
  • p
    Not clear why at this point: could be interaction of alpine+htmx, or htmx
  • s
    or set it to 0 anyway
  • s
    and let the browser doa full request on back button, since my site is stateful anyway i don't want a stale version shown.
  • p
    It could be that history cache is the issue, but if that is the case, default behavior should be to disable cache
  • p
    (with htmx)
  • s
    need to set cache headers from the server for it though, but if you have a log in system then in general you want to disable all caching so a person can't just read the data from a logged in user after his session is over.
  • s
    it might be that you geta miss on the history cache in which case htmx defaults to requesting the url and doing a swap.
  • p
    yeah there's all kinds of complexities here. I have a site using turbo and none of these issues appear, so I might dig into their source and see what they do
  • s
    I just decide to do a full restore on back button and disable all caching both from htmx and the browser, I reason that compared to normal navigation it is a fairly rare event.
  • p
    hmm
  • p
    so the docs imply https://htmx.org/docs/#history that using hx-push-url is required to explicitly snapshot and cache the DOM. But I'm not using hx-push-url anywhere
  • p
    "When a user hits the back button, htmx will retrieve the old content from storage and swap it back into the target, simulating "going back" to the previous state."
  • p
    thing is I'm not using hx-push-url and I'm seeing this behavior
  • p
    maybe hx-boost is doing it implicitly?
  • p
    but this is happening with an explicit hx-get
  • p
    so far it looks like hitting back/forward browser buttons re-triggers an hx-get on the page, even though the hx-get is not doing a full page transition and I'm not using hx-push-url
  • p
    furthermore: the hx-get fetches modal content into a div element. When I hit the back button it re-fetches and re-adds the same content into the div target, so I end up with 2 modals. Repeat, 3 modals and so on. Even though I've set hx-swap="outerHTML", so even if it does refetch, it should replace all content.
1...240241242...1146Latest