https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • a
    and that the whole thing is fake
  • b
    guys, i did someting and it worked and i'm suprised that it worked haha, basically i activated hx-boost in my href links but the server sill responding with the entire and its inner content, not the "partial body content" only , does hx-boost happens to select the tag of the response automatically(like hx-select) to swap with the current ?
  • m
    It does
  • c
    I read the hx-boost page but I am not sure if I get it. Why would I want to do that? i can think of: - only the main page defining head and not the others - avoiding history Is that it or am I missing sonething?
  • b
    thank you!!
  • s
    I tried using alpine-morph. It does the job of preserving alpine state, but it ignores (modified) HTML coming from the serfver. I then tried using idiomorph. It does the job of morphing (modified) HTML from the server, but the modified HTML doesn't have alpine state at all. What is the right way here? If I want to have new HTML from the server applied and at the same time, preserve Alpine state?
  • g
    how do people use 
    hx-boost
    successfully when the 
    <head>
    might have different 
    title
    / `script`/ 
    link
    tags on different pages?
  • s
    When I have multiple elements pointing to the same hx-indicator, then after the request is completed, the 'htmx-request' class doesn't go away
  • m
    this sounds like a very annoying bug
  • m
    i'm doing some htmx work, can you log a github issue and I'll look at it?
  • m
    looks to be an easy fix
  • m
  • m
    allowing you to modify attributes and then reinit the node
  • m
  • m
  • s
    Wow, thank you!
  • p
    I am using 
    hx-trigger="sse:eventName"
    to trigger a get request when there is an 
    eventName
    event coming over Server-Sent Events. I currently have this on each row 
    sse-connect="/row/<id>/progress-events"
    . I. wonder if I could have a single 
    sse-connect
    on the table and use the data of the event to filter. Something like 
    hx-trigger="sse:eventName[data=<id>]"
    (where 
    <id>
    would be the actual id).
  • g
    any thoughts on this from anyone?
  • g
    in a worst case with 
    hx-boost
    i may actually have a little (gasp) jQuery in my head to initialize things like bootstrap modals (eg 
    $(document).ready(...)
    )
  • l
    You'd be surprised at the perceived performance boost those things give you. Not only are they already downloaded, they're already parsed and ready to go. Plus, it's a nice on-ramp to the rest of htmx. Plus, it doesn't "avoid history" by default; it pushes by default.
  • g
    it will probably be redundant with paint holding and shared element transitions
  • l
    In my practice, the answer I've worked with is "don't boost if you want to change the head". That being said, though, it's entirely valid to put a script tag at the foot of the body that will do that initialization; it doesn't have to be in the head.
  • g
    yeah thats where i was headed... i was experimenting with that last week and hitting some challenges, course now I can't remember what they were... I think things were getting double initialized in places, I'll have to have another play with it
  • c
    https://htmx.org/attributes/hx-boost/ says nothing about "already downloaded" or "parsed". Does it predownload things? should more details be added there?
  • l
    If you're not changing out the head, some things may not need to be reinitialized. 🙂 Of course, you might be able to do a little defensive check around that init. 
    hx-boost
    is a good starting point, but once you get deeper into htmx, you'll likely find that you start breaking up your pages a bit differently.
  • l
    It's already there by virtue of the fact that you've downloaded the page containing the `hx-boost`ed link; the scripts and styles on that page are the ones I'm talking about.
  • c
    AH I see.
  • g
    Oof I just ran into this bug, when's the general release 😂
  • m
    hoping next friday
  • g
    anyone have a favorite generic way for handling 500's on htmx requests? I've got good error handling in the places where it makes sense but it would be nice to have a catch-all for uncaught 500's so that the UI at least does something for the user
1...843844845...1146Latest