https://htmx.org logo
Powered by
# htmx-general
  • c
    Yeah, I understand. unfortunately, I have to wire up some 10 or more event handlers, which makes for a bit more convoluted code. But that would fix it
  • c
    Just tried that, but unfortunately the problem remains...
  • c
    I'm switching between several sub-pages, and every time I navigate back to this page, the onLoad will get executed and another click-eventlistener is added. DevTools shows them referring to different scripts as well.
  • m
    OK, final trick: set a data attribute on the button when the event listener is added
  • m
    Copy code
    js
  let btn = elt.querySelector('#btn_request_logs')
  if(btn && !btn.dataset.initialized) {
    btn.dataset.initialized = "true"
    // add event listener, etc...
  }
  • m
    was thinking more about this, and I didn't like that htmx didn't support this use case out of the box, so I've added a new temporary class, 
    htmx-added
    that you can write your transitions against. The core problem here was that the 
    htmx-settling
    class was added to the target, rather than the added content, which makes it hard to write a transition only for new stuff. 
    htmx-added
    makes it easy. Will go out w/ the next release of htmx, 1.6.0, this weekend
  • n
    That's amazing! Thank you
  • m
  • m
  • m
    Is there anything like turbo frames in htmx?
  • r
    Very sick releases
  • r
    we're still in stealth mode, but htmx is being trialed / integrated as the core frontend tech at this company. When we enter public beta I'll post the showcase.
  • r
    htmx is a highly underrated system in a world full of react wannabes. Beauty in simplicity.
  • m
    hx-target is the concept in htmx. You can read the docs here: https://htmx.org/docs
  • m
    🙂 that's great to hear
  • m
    Wow slick release!
  • m
    You should look at Laravel livewire, it’s such a complicated mess compared to this
  • p
    I am learning HTMX and I have written a blog post that I want to release to the world next week. If somebody is willing to proof read it, here is a PDF version of the post. It uses Spring Boot and Thymeleaf on the server side and builds upon my implementation of TodoMVC (https://www.wimdeblauwe.com/blog/2021/09/20/todomvc-with-spring-boot-and-thymeleaf-part-1/). I am especially interested to learn if I am using it in the "good way", or if there are maybe things that can be improved.
  • m
    Hi wim, one piece of feedback:
  • m
    here you might be better off moving the 
    hx-
    attributes up to the form and letting the natural 
    submit
    event trigger the request
  • m
    then you don't need to capture the enter keystroke or rewire the submit event on the form
  • m
    Also, you might want to target the entire form, w/ all the todo's rather than using scripting to clear the input:
  • m
    a little easier to decompose
  • p
    Would that also automatically disable the form submit?
  • m
    yes, it would
  • m
    yeah, I think by rerendering the entire todo list, you can save yourself a lot of client side code
  • m
    if you are willing to do that
  • p
    But then I need to return the full html of all todo items, I like returning just what you added only better.
  • m
    That's fine if you prefer that. It'll just be more client side work. My bet is that perf-wise (if that's what you are worried about) it would be negligible to rerender the whole list. But to each his own.
  • p
    Could be, but you also need to refetch all todo items from the server to render all that html.
1...375376377...1146Latest