https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • q
    The thing is the input doesn't actually change other than it was focused and then not.
  • w
    Not sure if this applies to your situation but in your hx-post you can add an anchor to the url. That way you can keep focus on the element that initiates the request. Check out https://beschikbaarheid.heerenveen.nl/ for an example. Gotta run now.
  • l
    I could have sworn I did this in the past, but I can't find it now: is there a simple way to scroll to the top of a replaced element? i.e. I'm clicking the submit button in a form, and it replaces the submitted form with a new element, can I get the browser to scroll to the beginning of the new element?
  • m
  • m
    sounds like you want 
    show:top
  • l
    That's it, thank you!
  • e
    Is there a way to ensure our JS runs after HTMX has processed things? Context: We want to change the hx-get of an element based on the # of the url, then trigger that element's hx-get.. but we're not seeing anything happen at all. I assume this means htmx hasn't prepared that node yet, but not sure
  • e
    do i have to call 
    htmx.process
    after changing the element's 
    hx-get
    attribute? or is there a better way to change what url is got?
  • e
    doing that ^ does work.. i.e.
    Copy code
    element.setAttribute('hx-get', newPath);
htmx.process(element);
htmx.trigger(element, 'someevent');
  • e
    Hmm. looks like https://htmx.org/api/#ajax is probably what I want actually
  • e
    Copy code
    htmx.ajax('GET', newPath, {target: '#whatever', swap: 'innerHTML'});
    yeah.. this seems right
  • m
    I'm new to htmx and i keep hitting "well how would i do X". Right before I start a message on here I just stare at the htmx attributes. Not even looking at the contents, just the links. Then I feel dumb, do the simplest thing and move on. Its liking rubberduck driven development but somehow dumber.
  • h
    It makes a lot more sense when you just start using it
  • h
    You have to adjust your mindset a bit
  • b
    All right. Another week I resisted the urge to download jquery and do it the old way. 🙂 HTMX for the win!!
  • a
    What's the difference between`hx-vals` and the 
    include-vals
    extension?
  • r
    syntax
  • r
    also, hx-vals was added after include-vals, so most likely it is kept for compatibility
  • r
    Any ideas on how to deal with 
    hx-trigger="revealed"
    getting missed due to very fast scrolling or a refresh when at the bottom of the page (which would skip the to-be-revealed item). Context: I'm building an infinite-scroll feed with a catch - I don't want the last item to trigger the next batch, I want it a bit before.
  • m
    might be worth implementing your own javascript logic if the current logic isn't catching it
  • r
    It's tiny bit hacky, but here is an idea
  • r
    yeah that's exactly what I'm doing, basically for N items I'm putting the 
    hx-get + hx-trigger=revealed
    on the 
    N-X
    item which gives a little head start to load the next items. Unfortunately sometimes 
    htmx
    is missing that the item has been revealed.
  • r
    That's what I thought. My idea is to put a wrapper div over last X items, not just N-X item, so that hx-get is triggered if any of the last item is revealed, event if the user scroll past N-X item quickly
  • r
    This might break the layout, obviously, but it's the simplest option I can think of
  • r
    Alternatively, you could make a hidden empty div with absolute positioning to keep elements flow intact
  • r
    Yeah a wrapper would break the layout, but the absolute positioned element might do it. I’ll have to calculate how many elements I have left between N-X and N to determine its height I guess. Thanks @ripe-action-67367
  • s
    How to delete element with 
    hx-swap-oob=true
    in response?
  • r
    hx-swap-oob=delete
  • r
  • s
    Great, thank you very much
1...102410251026...1146Latest