https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    do not allow others to perceive you as a threat, stay hidden
  • m
    and slowly siphon off the competition before they even realise you're shoulder to shoulder with them
  • m
    then strike!
  • t
    hbo's silicon valley vibes
  • g
    one of the guidelines on the site: > Wish to pursue open source work full-time are you prepared to step away from teaching if that's what they ask you to do? 😬
  • m
    I'm not, it looks like it's 10 hours a week though.
  • g
    ah okay cool
  • t
    1cg is still n/a 😦
  • b
    Hi
  • f
    Hello, I have a general question with Hx, when you delete an element from a list which is also currently opened in the view and url. Do you stick to Hx and detect that the current element has been deleted to get again and push a new url. Or do you just stick to simplicity and redirect the full page.
  • f
    It comes to a more general question, how far should you go with Hx
  • b
    What do you suggest to do to fill a list of 
    <option>xxxx</option>
    from HTTP Get response ?
  • t
    Just return a list of 
    <option>
    tags. Or return the whole 
    <select>
    element and 
    hx-swap="innerHTML"
  • b
    Thanks. That was my idea too 😉
  • t
    This sounds like a personal preference / project requirement thing. You can definitely handle it with htmx in any way you want to. You could just show a message alerting the user that the current element has been deleted and will be gone when they leave the page, or you could force the page to change and then alert the user as to why that happened.
  • b
    Is it possible to perform a HTMX Get when the page is loaded to by example fill a 
    <select/>
    ?
  • t
    Yes, 
    hx-trigger="load"
  • b
    Gotcha 🙂
  • t
    for additional options
  • f
    when using
    Copy code
    hx-get="/notes"
hx-trigger="refreshNoteList from:body"
hx-vals='js:\{id: event.detail.value}'
    hx-vals is also added to child elements, I haven't found a way to avoid it
  • f
    it's a problem when the child element is also doing a hx-get but don't want those vals
  • f
    I've tried hx-disinherit="*"
  • f
    and hx-val="" it didn't work
  • f
    a bug maybe?
  • l
    Are there any htmx+hyperscript component libraries available? no problem paying
  • g
    hey, is there a way to activate/deactivate htmx on elements programmatically/after page load? i see that there's 
    hx-disable
    , but only its value when the page is loaded in seems to have any effect; toggling it after the fact doesn't seem to.
  • g
    i'm trying to prevent double clicks on certain buttons, i.e. second clicks on effect-having POST links by impatient customers while the first request is already in flight. temporarily deactivating the button seems like the best way to do it (but open to other suggestions). thx!
  • m
    I think in your particular case, this is what you want: 
    hx-trigger="submit queue:none"
  • m
    (Or whatever your existing event is—`click`, etc—plus the 
    queue:none
    modifier)
  • m
1...898899900...1146Latest