https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • t
    I think
  • h
    yea that would be ideal
  • h
    hx-trigger=" keyup  from:#search_form input, search, submit"
    works
  • h
    but interestingly the 
    changed
    modifier breaks it
  • h
    I'm thinking that might check the changing value on the element receiving the event and not the one triggering it
  • h
    huh actually no, that drops a syntax error in the console
  • h
    although it does work
  • h
    Child selectors don't work here
  • h
    yeah I wonder if this is a bug - hx-trigger + from + "changed" never fires
  • h
    also for the original question - the event does bubble, and 
    hx-trigger="input delay:500ms, search, submit"
    will catch all child inputs
  • h
    any reason to use keyup instead of input?
  • m
    keyup should bubble
  • m
    yeah, it's the 
    changed
    modifier: it is checking the 
    value
    of the form, which is always null
  • m
    we should at least have an option to make that the value of the event target
  • j
    hey i got around to trying this and it didnt seem to work. I think its because it is in a 
    hx-vals="js:"
    tag so even if it ends up being 
    hx-vals="js: unset"
    in the end it still tries to send it as it wasnt unset at the start. Am i doing something wrong?
  • r
    Just use hx-vals="unset"
  • c
    Hello, using hx-boots on links that load new data, it works great but always scroll to new loaded data
  • c
    are there some possibility to disable this behaviour ? Or just I missing something ?
  • s
    I mean rust/c/zig implementation of renderer
  • b
    Yep this should work if using the most recent version of htmx
  • b
    Before that, hx-vals=“unset” didn’t work iirc
  • s
    I'm having trouble replicating the delete row example (https://htmx.org/examples/delete-row/). The hx-delete request is sent and works fine, but the row is not removed from the table. I've tried returning both a 204, and no response at all. Anyone have any idea what i am doing wrong? Code below:
  • s
    Copy code
    <button type="button" class="flex items-center text-red-300 hover:text-red-600 focus:outline-none"
hx-trigger="click"
hx-delete="{{url_for('main.show_own_products_edit_row', product_id = product.id)}}"
hx-target="closest tr" 
hx-swap="outerHTML swap:1s"
hx-confirm="Are you sure?" >
  • s
    i dont thik you need the hx-trigger or hx-swap attribute for it to work,
  • s
    the problem is more likely that your framework returns 204 status code and htmx read this as 'no work to do'
  • s
    change it to an empty 200 response and it will work
  • s
    Perfect, thanks. The 200 worked! The hx-trigger is probably not neccecary, but works anyway.
  • a
    just built a table with column sorting on click and infinite scrolling, all with only htmx, and it's so beautiful
  • w
    curious @ancient-shoe-86801 , when sorting by column, are you getting a whole new set of table rows from the server to replace all existing data?
  • a
    on this case, when the user clicks on the header of one column, it will fetch a new table (header + rows) and replace the current one. I am doing that because the header changes to show what column you are sorting on.
1...957958959...1146Latest