https://htmx.org logo
Powered by
# htmx-general
  • g
    Gotcha. Try giving your server the ability to return each page in one of two states: either "wrapper+content" (if no 
    hx-request
    ) or simply "content" if the header is present.
  • a
    The thing is, the "content" is slow to load (lots of external api calls + processing)
  • g
    That way, on first load, your whole page gets rendered in one go. It will render quicker because you're only going over the wire once, and it takes the same amount of server resources (or maybe less, because fewer http requests).
  • g
    Yeah, that's trouble, then.
  • a
    Unless I'm trying to be clever by serving a cached version of the content with the wrapper and then updating the content with a fresh version doesn't seem like I've got much choice really
  • g
    Server caching is awesome 🙂 It'll save you a ton of work.
  • g
    But, if that can't be avoided, I understand.
  • a
    Fair enough, well I appreciate learning more regardless 🙂
  • a
    Now to see if I can get to the bottom of this screwy back button behaviour 😦
  • a
    Haha
  • g
    There really aren't any hard rules, because so much depends on your specific app and content. I'm making (essentially) a CMS, so each page is relatively cheap. There are only two parts -- wrapper and content (that can be dynamically updated). So, it makes sense for me to have those two rendering options.
  • g
    If you have some "expensive" parts of the page, your best bet is to encapsulate these as their own widgets that are rendered individually -- which is sounds like you're already doing.
  • g
    Good luck on the project! If/when you have something you can show off, I know everyone here would love to see the results of your work!
  • a
    Thanks @User, I will do!
  • a
    Won't be exciting though I warn you 😄
  • g
    Hello all 👋 What’s the best way to re-load htmx after the DOM has changed? I have a listing with an infinite scroller and the newly added items don’t work with htmx, so I need to make htmx aware of them somehow...
  • g
    Hey @User -- htmx triggers a number events when new content is swapped in. https://htmx.org/reference/#events If you have JS components in your newly added DOM, try making an event listener for 
    htmx:afterSwap
    and initialize the components then.
  • g
    Does that make sense?
  • g
    Hey, it's the other way round – I'm adding the new items with a separate script, so once these new items are added I need to make htmx aware of them.
  • g
    Oh, gotcha. There's a way to make that work, too. One sec.
  • g
    You can tell htmx about new DOM nodes you've added separately using 
    htmx.process()
    https://htmx.org/api/#process
  • g
    This is exactly what I'm looking for, thanks!
  • g
    I did scan over that but wrote it off for some reason 🙄
  • g
    Good. I'm glad that will work. Isn't that always the way it is with documentation? 🙂
  • g
    Works beautifully 👌
  • s
    i made a multiplayer geoguessr game with htmx that im playing on my stream here https://www.twitch.tv/guardsmanbob if anyone cares, its only intended to work when i stream though 🙂
  • b
    The amount of activity in the #796428329531605032 channel is impressive!! I just hope that htmx isn't "history" 😉
  • m
    lol
  • m
    we need to get the history bug worked out
  • m
    btw, thank you for doing the issue gardening
1...152153154...1146Latest