https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • c
    You were right
  • c
    Just tested it, works
  • c
    by any chance
  • c
    any idea how to access the current item in an x-for other than x-text ?
  • c
    i wanted to pass that x-text value as a parameter into that url
  • b
    What's the framework?
  • c
    its a template
  • c
    thymeleaf
  • c
  • c
    i found this
  • c
    was going to test it
  • b
    They're a good link in the #940241072959922176 channel on thymeleaf
  • c
    okay thanks
  • b
    Quick question about hx-trigger modifiers: what is the correct order of modifiers for 
    hx-trigger="keyup changed from:#foo delay:500ms"
    ? No amount of reordering seems to work! Demo here, if anyone can lend a hand: https://codepen.io/benlenton/pen/bGvOQWY?editors=1001
  • m
    unfortunately the "changed" modifier is applying to the div, rather than the input
  • m
    🤦‍♂️
  • m
    can you move the trigger to the input?
  • b
    Ah I see! I'm struggling to see how I could in this scenario.
  • m
    you could write a filter
  • m
    it'd be ugly but it would work
  • b
    So moving the 
    changed
    modifier to after the 
    from:
    doesn't alter the target of "changed"? e.g. 
    hx-trigger="keyup from:#foo changed delay:500ms"
  • t
    Just move the trigger to the input and add an 
    hx-target
    attribute to make it target the div
  • t
    Copy code
    html
<div id="bar">
  --
</div>

<input id="foo" hx-trigger="keyup changed delay:500ms" hx-get="/bar" hx-target="#bar">
  --
</input>
  • b
    Unfortunately the irl example is a bit more complex than that. I'm trying to put together a simplified demo now, because I'm probably missing a simple solution
  • t
    Is it so complex that you can't give the target an id to put into your input?
  • m
    we can figure something out
  • m
    frankly it's a bug
  • b
    The input is inside an hx-boosted form which can be submitted by various triggers. Moving the trigger to the input is an option, but I was struggling to see how the other enclosed form values would be submitted. I've found a workaround by using 
    hx-include
    , but is there a way to make the input still trigger the form submission instead?
  • b
    please don't ask me to raise a PR please don't ask me to raise a PR 😆
  • b
    I actually found another bug a while back and still haven't got round to raising an issue/PR for it. One day soon!
1...782783784...1146Latest