https://htmx.org logo
Powered by
# htmx-general
  • g
    the more complex the form, the more you want client side validation. you want faster feedback, if the form is 10-15-20 inputs long, you don't want to wait until the end to show a mistake in the beginning
  • g
    but that's not really my usecase here anyway.
  • g
    Have anyone done anything regarding deploys that touch stuff that won't normally be loaded again with a boosted site? Like css / js that is included in the html head.
  • g
    Turbo does this: https://turbo.hotwire.dev/handbook/drive#reloading-when-assets-change and I was thinking about making something similar. But wanted to check if that is something that is already solved 🙂
  • g
  • g
    I agree with @sparse-musician-64201 The most my forms will do is show/hide optional elements based on inputs, but it’s the same form being posted, no matter what.
  • g
    I’d also add that it’s awesome to use the same “model” to generate front end and back end validation. That way, you’re always validating inputs in both client and server, and the results are always the same 🙂
  • g
    We did something like this to prevent boosting of links / forms with data-remote="true": htmx.on('htmx:beforeRequest', (e) => { if (e.detail.elt.dataset.remote === 'true') { e.preventDefault() e.stopPropagation() } })
  • g
    https://github.com/bigskysoftware/htmx/pull/408 @User minor update to the docs to add something to the index list, cause i didn't see this at first and did things the very hard way haha
  • m
    awesome! I want to put together a third party section in the docs, are you willing to start it and add this example?
  • g
    https://htmx.org/docs/#css_transitions just to be clear on the docs here; this only works with out-of-bounds swaps, right? because i tried this:
    Copy code
    <button hx-get="test-transition" hx-target="#transition-demo">Test Transition</button>
<div id="transition-demo"><p>This is empty.</p></div>
    The response is:
    Copy code
    <div id="transition-demo" class="red">
  <p>This should transition to red.</p>
</div>
    but that didn't actually work. it just swapped immediately, there was no css transition.
  • g
    oh, it does work with hx-swap="outerHTML".
  • g
    interesting.
  • m
    it should work
  • m
    we match everything up by id
  • m
    if it isn't working, that's a bug
  • g
    it doesn't work without the 
    hx-swap="outerHTML"
    for whatever reason
  • m
    Ah, maybe the content is gone when we try to look it up...
  • m
    That might be a legit bug, can you log it?
  • g
    i can try but i don't understand it exactly.
  • m
    "CSS transitions don't work with `outerHTML`" swaps
  • m
    nothing works properly with outerHTML swaps
  • m
    outerHTML swaps are the IE of swaps
  • g
    wait; it's the opposite
  • g
    css transitions are only working for me with outerHTML swap
  • g
    in the example I gave
  • m
    lol
  • m
    AHHH
  • m
    OK, if you don't target the outer html, you are ending up with a nested div
  • m
    two divs, same ID, htmx gets confused
1...177178179...1146Latest