https://htmx.org logo
Powered by
# htmx-general
  • m
    yeah, htmx isn't that smart yet
  • m
    :/
  • m
    sorry guys
  • p
    yes: the implication from the docs is that htmx.process fixes that
  • m
    I am gonna start working on it again next week, I promise
  • m
    the docs imply wrong 😑
  • p
    "This can be useful if you have content that is added to the DOM outside of the normal htmx request cycle but still want htmx attributes to work."
  • p
    that's exactly the use case here
  • p
    this line
  • p
    if (!explicitAction && getClosestAttributeValue(elt, "hx-boost") === "true") { boostElement(elt, nodeData, triggerSpecs); }
  • p
    looks like it should work
  • p
    tried adding hx-boost to immediate parent, that didn't work either
  • m
    yeah, once a node is initialize, it won't re-init
  • m
    😑
  • m
    it should, but it don't
  • p
    hmm I have an idea
  • p
    if I can somehow destroy the node in question & recreate it
  • p
    no that didn't work either, htmx doesn't process it at all (i.. hx-boost stops working)
  • m
    you'd need to reinit the node after that
  • m
    :/
  • p
    yeah but htmx.process doesn't work
  • p
    looks like htmx doesn't play well with dynamically generated links
  • p
    I'll need to rethink things a bit
  • p
    maybe generate the content directly with htmx (i.e. pull from server) rather than update dynamically with alpine
  • p
    yeah again the only thing that works is using hx-disable
  • p
    ok found the solution
  • p
    <a :href="episode.url" @click.prevent="htmx.ajax('GET', episode.url)" hx-disable class="player--title" :title="episode.title" x-text="episode.title">
  • p
    in alpine, ":" shortcut sets attributes and "@" events (like VueJS)
  • p
    hx-disable stops normal htmx execution (in this case hx-boost sending to old URL)
  • p
    "@click.prevent" does a event.preventDefault() so stopping a full (non-HTMX) page navigation
1...239240241...1146Latest