https://htmx.org logo
Powered by
# htmx-general
  • b
    ^ on my server I check for hx-boost header and conditionally full/partial, works quite well so far
  • u
  • m
    > In the end, htmx is for any backend tech, but I guess the opposite should also be true. Your backend tech shouldn’t be too coupled to your frontend libs... excellent thinking
  • a
    I read (skimmed) through about half that … I think I need to go lie down for a bit now…
  • u
    Had the same reaction...
  • m
    rather elaborate
  • t
    I'm using hx-boosting on my site and there are a few pages where I'd like to be reloaded when the back button is pressed instead of showing the old page. Is there any way of doing this inside of htmx or would I need to rely on jquery for this?
  • m
    You could set the local cache size to 0, so htmx always issues a full page restore
  • m
    let me look to see if there's a way to make it page specific
  • m
    no, unfortunately doesn't look like there is a page specific mechanism. Could look at adding one if you want to create a github issue explaining the issue
  • t
    thanks for looking into it!
  • t
    i'll add an issue, i think this might be pretty useful to show updates as users navigate back
  • t
    i'm interested in contributing, do you think this one might be a good place to start?
  • t
    or would this involve a significant or complex change?
  • m
    sure
  • m
    no I don't think so
  • m
    for stuff like this I tend to lean towards "trigger an event, let the user tell me what to do w/ the event"
  • m
  • m
    another thought (not necessarily a good one): what if we triggered an event somehow that allowed elements to refresh on history restoration?
  • m
    Copy code
    html
  <div hx-trigger="htmx:restored" hx-get="/whatever" ...>
     ...
  </div>
  • m
    maybe a little too fine grain
  • m
    you are using boost, so you want this to "just work"
  • t
    i really like the idea of it being element based
  • m
    it's funny, 
    hx-boost
    was kind of an afterthought, but it is very widely used
  • t
    but also a general per-page reloading would be great
  • t
    i would think that there would be plenty of use cases where data is modified, a user goes back and expects for a part of the page to be updated. however, the entire page might be costly to render entirely
  • m
    OK, well have some fun with it!
  • t
    awesome, i'll dig in. thanks for the help!
  • f
    Hey, just a quick question – how do I make another div listen for when a button is pressed without registering it with JS?
    Copy code
    html
<div id="sidebar">
  <button id="open-sidebar"><
  <div id="sidebar-content1" hx-trigger="click from:#open-sidebar" hx-get="/xapi/sidebar1">
  <div id="sidebar-content2" hx-trigger="click from:#open-sidebar" hx-get="/xapi/sidebar2">
  <!-- ... -->
  </div>
</div>
  • f
    PS: Am I the only one who seems to struggle with figuring out events the first time? Once I figured out use-case X it's obviously easy to c/p, but without any prior JS background it feels like hit or miss on the initial try.
1...385386387...1146Latest