https://htmx.org logo
Powered by
# htmx-general
  • m
    this sounds like it might be back end specific, is there a channel in the Stacks group that might help?
  • h
    I will try to find..... 👍
  • t
    What does this mean? > The HX-Location response header now implements client-side redirects entirely within htmx
  • r
  • r
    Basically, HX-Redirect alternative without reloading the page
  • t
    Oh right this is a new header, not a change to the hx-redirect header. My brain just went "yes, location and redirect are the same word".
  • p
    🤔 Should I be able to use 
    *
    selector in 
    hx-select
    ? Something like 
    hx-select="#myid *"
  • t
    What would you expect to happen there?
  • p
    Select everything under 
    #myid
    ?
  • t
    And put it where?
  • t
    Or I guess in other words, how would that be different from just selecting 
    #myid
  • p
    Good question! I'm building a load-more button that looks like...
    Copy code
    <a id="load-more" class="button" href="{{ url }}"
    hx-get="{{ url }}" 
    hx-swap="outerHTML" 
    hx-select="#list article, #load-more, #no-result">{{ 'THEME.PAGINATION.LOAD_MORE'|t }}
    </a>
    When swapped, the button itself is replaced by whatever should be appended to the list. I currently use 
    hx-select="#list article, #load-more, #no-result"
    but was wondering if I could simply use 
    hx-select="#list *"
    .
  • t
    Have you tried?
  • p
    I did. And you know what? I think I fell for the oldest trick in the book.... cache
  • p
    Seems to be working.
  • t
    Neat
  • b
    Love it! Was just browsing the docs and saw here https://htmx.org/headers/hx-push/ that 
    HX-Push
    has become 
    Hx-Push-Url
    . Should this be reflected in the response headers section, which currently still refers to 
    HX-Push
    ? (https://htmx.org/docs/#response-headers)
  • r
    Hyperscript on HN again:
  • m
    yes, pull request please!
  • m
    finally got my roy fielding JSON API meme right
  • h
    I did that - I did it because django has a lot of redirect based stuff (post form/post login, ect) and I didn't want to blow away the dom when doing that
  • t
    I understand it, I was only confused because in my brain I conflated hx-location with hx-redirect
  • t
    When I read it I thought hx-redirect had been changed
  • e
    hx-select-oob
    is super interesting for the extension I built. Basically made a custom attribute doing something very similar (using a very sketchy string replace to inject 
    hx-swap-oob
    into html chunks I get from the API), but it also sends the selected ids with the request. I wonder if I could somehow unify them or just lift the logic for that attribute in 
    handleOutOfBandSwaps
    ?
  • e
    There doesn't seem to be a nice way to hook into 
    handleOutOfBandSwaps
    to get 
    settleInfo
    except 
    handleSwap
    , which isn't called when a swap style is explicitly defined
  • l
    In docs, I don't see anything for 
    HX-Replace-Url
    and there are two different links giving 404s. I do see the changes to 
    HX-Push-Url
    , and I'm guessing the behavior is the same, just replaces instead of pushes. (I was going to PR to fix the links, but there's not a page under 
    /www/headers
    .)
  • l
    I'm guessing the implication of the URL push on POST is that the POST-Redirect-GET pattern ends up at the right place without having to jump through some hoops? (If so, that's awesome!)
  • m
    PR please, and yes
  • m
    man, htmx is fun sometimes
  • a
    Using the 
    client-side-templates
    extension is there a way to run 
    htmx.process
    or equivalent on the rendered output to hook up htmx behaviors / hyperscript in the template?
1...743744745...1146Latest