https://htmx.org logo
Powered by
# htmx-general
  • m
    the best of all possible worlds
  • a
    Can I ask a question here?
  • m
    you sure can
  • a
    I just posted this at r/htmx/ , here: https://www.reddit.com/r/htmx/comments/s9r231/how_to_save_multiple_htmx_created_forms_in_django/ The question is, what is the way to go about saving several of the same forms created with htmx in django, since request.POST will give you a list of the values like so: {'Person-first_name': ['One', 'Two'], Person-last_name': ['Onelast', 'Twolast'], 'Person-age': ['', '40']}
  • m
    this seems pretty django-specific, the folks in #864934037381971988 might have a better idea what's going on
  • a
    Sorry guys, I posted in the wrong channel. Thanks for letting me know!
  • a
    I know I should feel bad for enjoying these things so much, but it is what it is 🤷‍♂️
  • s
    Loving the irony in the 'slightlylate' username 👌😄
  • m
  • b
    what are the patterns for unit testing htmx interactions
  • r
    Since HTMX breaks up my HTML responses more, I've done just normal HTML parsing and checking in the past. There are probably more comprehensive ways to test, like with cypress
  • r
    Copyright Google?
  • m
    it's almost like I copied that license from somewhere else
  • r
    Ah okay, thought you might have worked for them back then
  • m
    nope, I briefly interned there a long time ago, but my boss didn't have a sense of humor so I didn't last
  • p
    Context: when swapping a lot of HTML that also contains tags, there are some querySelector calls that take a long time, regardless of my attempts at setting hx-disable and disable-scripting to prevent recursion into those elements. This makes a page load turn into ~7s. Setting defaultSettledDelay to -1 helped, i think. Currently i'm looking at the "isBoosted" and "findElementsToProcess" as potential issues.
  • p
    Yup. confirmed it is "isBoosted" during a doSettle.
  • p
    Right now the logic is if the settleDelay is greater than 0, use a timeout, otherwise immediately doSettle. Perhaps a negative value could mean "don't worry about settling, skip it"? or check first for a htmx-disable?
  • p
    okay... there is a much easier fix: wrap the entire response into a single DOM element rather than a rabble of 1000's of individual elements. Much better for performance!
  • w
    Is there a way to cancel the scroll that happens on a boosted 
    <a>
    tag? Using 
    href="#" hx-get="/my-url/"
    works, but just figured I'd ask
  • s
    i solved it by not using boost but just writing the hx tags by hand
  • s
    i do wish that the scroll behavior on boost wasn't default, seems like a bit of a trap when using htmx on a top nav bar (which is even how it is used on the main site)
  • w
    Generally speaking I like the scroll behavior, but the ability to disable it would be nice
  • s
    perhaps hx-boost="noscroll" would be nice to have
  • w
    It also looks like boosted links don't respect 
    hx-push-url="false"
    but that could just be another issue on my end
  • s
    well, boosting is almost just a shortcut for pushing urls anyway, so at that point it probably makes more sense not to use the boost anyway
  • w
    Yeah, I suppose I was just hoping to avoid 
    href="#"
    links, but that's just me.
  • p
  • w
    Does 
    HX-Redirect
    respect the initial 
    hx-
    attributes of the requesting element? That is, if I had an element with 
    hx-target="#my-target"
    , should a response with an 
    Hx-Redirect
    also be swapped into 
    #my-target
    ?
  • m
    No, HX-Redirect is a pure client side redirect. If you do a server side redirect it will preserve the target
1...536537538...1146Latest