https://htmx.org logo
Powered by
# htmx-general
  • s
    ah, so had to switch to 204 in response and 
    hx-trigger
    to 
    every 1s
    instead of 
    delay:1s
  • m
    ah, missed that you were using load polling, sorry
  • s
    yea, I liked load polling better because it'd prevent multiple requests from happening at the same time (if, eg, one go stuck in some internet traffic haha), but every would work I think.
  • s
    do you think using something like morphdom would prevent the animation restarting?
  • m
    Might be worth a try
  • m
    i don't have a lot of experience w/ it, i'm actually looking at the source now 🙂
  • h
    in the slack today: > hey have you seen / figured out a clean way to do a delayed redirect with htmx? Right now I'm returning a template response that I want to be shown because it's confirmation of successful payment but I want to redirect immediately from there. So i was including the HX-Redirect header in my TemplateResponse but that's redirecting right away so you never actually see the confirmation. does that make sense?
  • h
    solution was
    Copy code
    <div 
   hx-target="body"
   hx-get="redirect url"
   hx-push-url=true
   hx-trigger="load delay:5000"
>
  • h
    I've done that exact thing so many times, that is super clean
  • m
  • m
    anyone ever used this?
  • m
    looks a lot cleaner than morphdom!
  • h
    I think I found a bug but I want to ensure I understand how this should work
  • h
    I have a page with
    Copy code
    html
<ul id="messages"></ul>
    and I am following a boosted a tag somewhere else, and the returned body swap contains a full page, including this:
    Copy code
    html
 <ul class="messages" id="messages">              
    <li hx-swap-oob="beforeend:#messages">
                <div class="text-lg font-semibold">Success</div>
                <div class="text-md">You have signed out.</div>
  
</li>
</ul>
  • h
    because the swap-oob is not at the top level I am expecting it to be ignored, and messages to be swapped out entirely, and the resulting page to include both the ul and li
  • h
    instead what I am seeing is that li is swapped into the old page, and then the new messages swaps out the old messages for a final result of an empty ul
  • m
    Ah, you are targeting the parent of that ul?
  • h
    yeah
  • m
    Yeah, that's gonna do exactly what you are seeing
  • m
    Are you trying to preserve the old UL content?
  • m
    you can't let the new content just ride along w/ the parent content update?
  • h
    no, tried with hx-preserve and because of some alpine stuff it reinits the message timeout
  • m
    I was going to suggest hx-preserve next 😑
  • h
    I have a middleware that makes it so when it's not a full body swap I get a bunch of 's trailing at the end of the fragment
  • h
    next idea is to use alpine-morph + hx-preserve and see if that will keep alpine state between pages
  • h
    is there a better structure I could use
  • m
    \> alpine state
  • m
    👏 I'm out
  • m
    😑
  • h
    it's not global though! it's stored in the html
1...720721722...1146Latest