https://htmx.org logo
Powered by
# htmx-general
  • m
    I tried with the # but no difference.
  • g
    replace the whole 
    [id=...
    thing with just 
    #comment{num}
  • m
    Got it - one sec
  • m
    Still not working here is the debug output
  • m
    post the html, that will be more useful
  • m
    The event is working and it is posting but the comment that is being sent to the backend is blank
  • g
    I see, you're using 
    contenteditable
    instead of an 
    <input>
    element. @User does htmx support that?
  • m
    Not sure. I did that because it was in a table. I can try changing it.
  • u
    Thanks! I managed to fix things up. Actually I was missing the point to where to put the event handling (it was not at the right div).
  • g
    I recommend it, you can put an input in a table cell just fine
  • m
    I will try. Thanks for all you help!!
  • m
    I don't believe so
  • b
    How do I handle the browser back button I want to confirm from user before leaving??
  • m
    you'd probably need to override the normal history handler and do it manually
  • m
    hx-include
  • m
    I changed it to an input and still no joy
  • s
    So I'm a bit confused with the syntax for hx-trigger: I wanna trigger on a click event of a child element. It's css-class is .item there is only one child with that class. If i read the docs correctly, the syntax would be:
    Copy code
    html
<div hx-get="..." hx-trigger="click from:find .item">
  <div class=".item"></div>
</div>
    But this thows a htmx:syntax:error without further information. Did i misinterpret the docs?
  • m
    find unfortunately isn't going to work in that context :/
  • m
    wait
  • m
    gimme a few
  • s
    oh, ok 🙂 i also could trigger that request in hyperscript, i believe from works there 
    _="on click from .item fetch..."
  • m
    ugh, OK, the docs are wrong here
  • m
    :/
  • m
    it half works, but isn't tested so that's what you are seeing
  • m
    yeah, hyperscript is the best option right now
  • m
    OK
  • m
    try this:
    Copy code
    html
<div hx-get="..." hx-trigger="click target:.item">
  <div class=".item"></div>
</div>
  • s
    ok, that does not trigger. I'm running a bit out of room there. I introduced the outer 
    div
    because the inner one is that one with the longpress behaviour we discussed the other day. It has his own trigger, url and target. I want to distinguish between a click and a longpress event. I'll give hyperscript a try then. Thanks!
  • m
    roger, sorry about that
  • m
    if you have time, a github issue would be appreciated
1...340341342...1146Latest