https://htmx.org logo
Powered by
# htmx-general
  • s
    you do need to learn how to extend the styles with variants though as the default set is limited, but as a bonus you get dark mode for almost free.
  • m
  • m
    now we can focus on hyperscript 0.0.4
  • i
    Is it a bug or feature that HX-Request is processed after a returned 302 response redirect? For instance, using 
    hx-post
    with a Log Out link that returns a 302 response with both a redirect and an 
    HX-Redirect
    header.
  • i
    I found the redirected page being loaded into the link, which was visually weird. 😆
  • m
    mmm
  • m
    the HX-Redirect combined w/ a 302 is a little funky
  • m
    can you detect if the request is from htmx or not?
  • i
    Oh sure, but it's an extra logic step. I was just attaching the header to the response directly, without checking if the request was from htmx.
  • i
    I was wondering if the exact behavior was "undefined".
  • m
    I would call it undefined
  • i
    I'm returning HTTP 204 with the correct header now, FYI.
  • m
    broadly, we want to respect redirects within partial replacement
  • m
    so you can do things like redirect output after a successful form save or whatever
  • i
    Interestingly, if it's a 302 with the correct 
    HX-Redirect
    header and you add 
    hx-swap="none"
    then nothing happens.
  • i
    No page change, no redirect.
  • i
    But the AJAX does follow the returned redirect.
  • m
    Right
  • m
    the redirect is of the AJAX response, not the page, right?
  • i
    I guess the final request only is scanned for the 
    HX-*
    headers?
  • m
    I don't know if we ever even see the original 302 response
  • m
    I think it's hidden in the ajax call
  • i
    Ah, that makes sense.
  • m
    iirc
  • s
    I beleive the spec correct thing to do would be for htmx to ignore everything on a 301 or 302 response and let the browser change the location.
  • s
    since that is more or less what it says on the tin: "the data you want is acutally over here".
  • s
    but i guess it gets somewhat wierd since its an ajax request, and maybe the right thing would be for htmx to reissue the request an process the data from it again.
  • s
    but i definitely don't think htmx should listen to anything on the 301 or 302 response it self. (but i am no authority on the matter)
  • m
    question for the group: AlpineJS has a way to toggle display:none via an https://github.com/alpinejs/alpine#x-show attribute. Is this the right way to toggle between things being shown and not shown? I'm considering adding something similar to hyperscript, but I wonder if opacity or visibility might be better. Thoughts welcome.
  • g
    I hate to ask for everything, but here goes: Alpine is clearly filling a need by making an simple way to show/hide something. The dilemma I see is that advanced cases usually have more sophisticated needs. For example, In many cases you might want to show/hide a nose and include a fade in/out animation in the process. So, while default settings are great for getting started, I can’t always use them in a real app.
1...157158159...1146Latest