https://htmx.org logo
Powered by
# htmx-general
  • a
    Here's the Stackoverflow page I invariably end up on everytime I try to tackle this problem: https://stackoverflow.com/questions/199099/how-to-manage-a-redirect-request-after-a-jquery-ajax-call
  • a
    Here's the crux of it: "No browsers handle 301 and 302 responses correctly. And in fact the standard even says they should handle them "transparently" which is a MASSIVE headache for Ajax Library vendors. In Ra-Ajax we were forced into using HTTP response status code 278 (just some "unused" success code) to handle transparently redirects from the server... This really annoys me, and if someone here have some "pull" in W3C I would appreciate that you could let W3C know that we really need to handle 301 and 302 codes ourselves...! 😉"
  • r
    Or if htmx just had a header that I could return (similar to the 278 work around) that would tell it to follow a redirect that would be fantastic
  • a
    Well... @User?
  • a
    On a COMPLETELY different topic: I've been using single a 27# external screen for the last 5 years. I just got a 34# Ultrawide today.... and it's weird. But now I'm thinking... if I'm gonna go weird... should I just not go for the full 2x 27# option, which is th e 49# ultrawide screen?! Thoughts? What do you guys rock for external screen sizes? Youtube is full of reviews by Final Cut Pro editor reviews... but not so many software developers reviewing ultrawide sceens
  • m
  • m
    what am I answering?
  • a
    this: "No browsers handle 301 and 302 responses correctly. And in fact the standard even says they should handle them "transparently" which is a MASSIVE headache for Ajax Library vendors. In Ra-Ajax we were forced into using HTTP response status code 278 (just some "unused" success code) to handle transparently redirects from the server... This really annoys me, and if someone here have some "pull" in W3C I would appreciate that you could let W3C know that we really need to handle 301 and 302 codes ourselves...! 😉"
  • a
    Or more specifically, this
  • r
    And this for motivation
  • a
    Dogpiling mission accepted. This message will self-destruct in 5..4..3..2..1....
  • m
    ah, yes, I share your frustration but also i don't know what to do about it
  • m
    I was surprised at the existing dog pile, I don't think we need to help too much!
  • a
    You're right.. Elon Musk may now safely abandon the falcon heavy and just climb aboard the htmx train to Mars 😁
  • n
    Hmmm @User @User hx-boost indeed solves the issue. I now have the cursor hover effect without added CSS and 
    Command + click
    works again!
  • n
    Just had to convert all 
    hx-get
    attrs to 
    href
    (or 
    method
    for forms)
  • n
    Nice that boost assumes 
    hx-push-url="true"
    becuse I could delete that in a lot of places
  • n
    that being said, why not have 
    hx-boost
    replace the element it's attached to?
  • n
    Currently I have to manually specify the 
    hx-target
    on each link
  • n
    They are all actually set to the same specific ID
  • n
    if boost replaced itself or let me specify the target globally, that'd be more config that get's removed.
  • m
    you can hoist the hx-target up the DOM and elements should inherit it
  • n
    of course
  • n
    that's perfect
  • n
    Man I'm loving HTMX so far
  • n
    makes you so productive with a backend framework like Django
  • l
    > when_is_it_time_to_use_react/ When you are tired of life, and desire to find the reason to self-harm you've always been secretly looking for.
  • l
  • h
    where should i put the htmx include sentence ? in the body or head part of my html? whats considered the best practise to use
  • r
    i'll upvote anything by @User
1...463464465...1146Latest