https://htmx.org logo
Powered by
# htmx-general
  • g
    If the fragment you’re loading doesn’t matter to htmx, then you don’t need to.
  • g
    Hope this makes sense?
  • g
    Yes, My Javascript isn't good enough to make sense of it though.
  • g
    I could handle this situation with AJAX, but trying to make it work with HTMX
  • g
    So here’s a question to help you sort it out. What happens on the server side of that GET? What’s in the content you’re loading with it?
  • g
    The issue might be I don't fully understand that snippet (because I don't)
  • g
    Translating…
  • g
    The content I am loading in is a element
  • g
    I think the issue might be in the snippet, and not HTMX
  • g
    Because I have to re-use it in the inserted content
  • g
    The snippet says: whenever content is loaded scan for nodes with class 
    cataddclass
    . Whenever those nodes fire a select2:select event…
  • g
    yeah, I have unique classes defined for that
  • g
    Trigger a “change” event on the select box.
  • g
    Yes, I’m not sure this is calling any external files. So you may not need to worry with htmx here.
  • g
    I need HTMX because the HTML I am inserting has variables that are filtered on my get call
  • g
    // In your Javascript (external .js resource or tag) $(document).ready(function() { $(".mattaddclass").select2({ theme: "classic", placeholder: "Select Material", }); });
  • g
    Gotcha. Just keep the html and JavaScript separate in your head. They’re both running in different domains.
  • g
    This seems to be the offending bit of code in the inserted HTML that won't allow the inserted HTMX to work
  • g
    What does the inserted html look like?
  • g
    So this is the first select: https://wtools.io/paste-code/b9WV
  • g
    And this is the inserted: https://wtools.io/paste-code/b9WU
  • g
    Ok. Looking…
  • g
    Thanks!
  • g
    Hoo boy, there’s a lot in there 🙂
  • g
    It looks like you’re generating two select boxes, then turning them into select2 widgets afterwards, yes?
  • g
    I’m on my phone, so doing this a little blind, but here’s my first thought:
  • g
    Right
  • g
    The first HTMX request works fine
  • g
    In the second script, those JS scripts are probably never going to run, because they’re listening for events that have already fired (and won’t fire again)
  • g
    That makes sense
1...604605606...1146Latest