https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • a
    Looking at using a Select dropdown as a nav and would love it i could trigger a get per it looks like it might not be possible currently?
  • a
    kinda like this in theory
    Copy code
    <select name="nav" id="nav">
        <option value="#">Where to?</option>
        <option value=""  hx-get="/addbatch" hx-target=".body">Add a Shipment</option>
    </select>
  • g
    It is a great demo of htmx’s extensions. There are some gotchas depending on your http headers. Of you use preload, make sure to watch your HTTP vary header to make sure your browser can use its cache effectively.
  • g
    Htmx is so simple/powerful, it’s enabling me to make an app that would be simply impossible to built otherwise.
  • s
    Sometimes people say that htmx is not for big projects. I think that's BS. Yesterday I read the Go style guide of Google. If the company with one of the largest code bases underlines simplicity over and over again, then this means to me: simplicity like htmx are even more important for big projects. But why is there no huge project using htmx? Time.... Big projects need time to be created or changed.
  • e
    Is there a way for me to get hx-get to include some form element values as URL parameters? I want a div somewhere in my form that I replace with some extra details depending on how the form is filled out (duplicate record check)
  • b
    Big projects sometimes small value.
  • b
    Many such...
  • m
    sounds like you want to combine hx-include and hx-push-url
  • e
    Aha, I was using hx-include wrong
  • m
    there are some big projects using htmx's predecessor, intercooler.js. @gray-oyster-51537 works at https://www.instawork.com/, and they have (or had) a really big intercooler app. So, they are out there, but no FAANG coverage yet. (I recently spoke at a FAANG, who is using it internally, so it's probably coming.)
  • m
    I think that the docs for this extension should mention the 
    Vary
    header and maybe link here: https://htmx.org/docs/#caching
  • m
    and, by "I think", I mean...
  • e
    Can I get hx-get to trigger when the form its div is inside changes?
  • m
    hx-trigger="change from:#some-form-id"
  • e
    Ah, too easy. Is that somewhere in the docs? I didn't see 'change' listed in hx-trigger, but I guess knowing that 'change' is an event and knowing about the from: option is enough.
  • m
    yeah, change is just a generic DOM event
  • m
  • b
    I have a set of radio inputs with hx-post and hx-swap=none where the request returns some oob content. The idea is that the radio inputs just do their thing and the rest of the page responds with oob responses
  • b
    The problem is that the radio inputs state is being reverted whenever one is clicked
  • b
    So the request goes through, but the clicked radio input stays the same. With dev tools open I can see the checked=false status flash to true then back to false immediately
  • b
    any ideas?
  • a
    Is it possible to include a name or some sort of identifier in my htmx get request?
  • a
    My problem is I'm using the same code on my backend to handle a htmx trigger from two different parts of my website.
  • a
    But they have to be handled slightly differently
  • a
    and I don't know how my backend can know which one comes from where
  • g
    why not just have two different paths, or a query parameter?
  • a
    I could do two different paths, and that's what I've done for now. I just thought since they are both doing basically the same thing it would be nice to just have one. Could you explain what you mean by query parameter?
  • g
    /url?thing=asdf
  • a
    ah yes that might be what I'm looking for, thanks for the idea
1...917918919...1146Latest