https://htmx.org logo
Powered by
# htmx-general
  • m
  • m
    regression added, works for me (tm)
  • m
    I remembered: try 
    htmx.logAll()
    to see all the events fired by htmx and what they are being fired on
  • m
    Using javascript in an extension, is there a way to get the instance of the triggering element within htmx events? I've been looking at the log for evt in afterSettle, and I can only find a reference to the id in evt.detail.requestConfig.headers['HX-Trigger']. In this case, the target is different than the trigger, and the trigger is within the target.
  • m
    looking
  • m
    looks like 
    evt.detail.elt
    should have the element that the event was triggered on: https://github.com/bigskysoftware/htmx/blob/c7bde5ad2587a53c5be3369803232757e4fdbfb8/src/htmx.js#L1499
  • r
    @User So it looks like 
    afterRequest
    fires on the form, but the 
    elt
    is actually the 
    hx-target
    object. I tried shrinking the form tag to: 
    <form hx-post="/path/to/" _="on htmx:afterRequest log 'Yes'">
    . The only thing that did was correctly leave the 
    form
    object as the 
    elt
    for the 
    afterRequest
    . I'm surprised that everything moves to the target and nothing stays on the original caller. For some reason, still no console log.
  • m
    😑
  • m
    Thanks. I am getting the target element there instead of the triggering element, which may be the right thing. Was just wondering if there was a better way to get the triggering element. Here's what my code looks like:
    Copy code
    html
<div id="yoyo-lmilgthy" hx-get="render" hx-include="#yoyo-lmilgthy *" hx-trigger="refresh" hx-target="this">
    <button hx-get="today">Today</button>
</div>
  • m
    🤔
  • m
    which event in particular are you referring to, I think we trigger the event on different things depending on context (see the unfolding disaster above)
  • m
    can you throw a 
    _='on click log "Yes"
    in there and just verify that hyperscript is working at all?
  • m
    This is on 
    htmx:afterSettle
  • m
    ah, OK, yes, for the swap related events, the event is triggered on the settled event
  • m
    Got it. I am going to check some previous event to see if I can store the triggering element to access later. Thanks!
  • r
    Well, for what it's worth the 
    on click
    isn't working either is hyperscript just isn't doing anything.
  • m
    🙂
  • m
    are you including the hyperscript library?
  • m
    I think we should include this in the request info
  • m
  • m
    we include a target, we can include a 
    triggerElement
    too
  • r
    ........ well... whoops
  • m
    you want to add it verify that it works locally and then make a pull request?
  • m
    lol no worries, we need to make clearer that they are two separate projects
  • m
    this is seriously a big issue w/ event driven programming: "why isn't x happening?"
  • m
    Sure. What do you want to call it, 
    trigger
    , 
    triggerElt
    ?
  • m
    Not sure
  • r
    Yes.. in my (slight) defense, I remember looking at that yesterday and no where in the htmx docs did it say anything about including/loading hyperscript separately and somewhat implied that some of it came with htmx. Minor, minor, but that works great now!
  • m
    triggerer
    ?
  • m
    Let's fix that
1...298299300...1146Latest