https://htmx.org logo
Powered by
# htmx-general
  • r
    @mysterious-toddler-20573 man.. dunno how possible this would be but if 
    hx-trigger="submit[action(target)]"
    just supported async, it would be suuuch an elegant way to perform event interception, and do anything, such as fetch auth tokens, etc.
  • r
    the Hotwire way:
  • r
    Currently, you can pass an async function in, but 
    maybeGenerateConditional()
    just doesn't understand it:
  • m
    i've had a few comments asking about async support, but that would involve promises which are not IE compatible
  • r
    it would totally dunk on hotwire to allow that imo 😂
  • r
    Documented:
  • s
    I'm contributing to a library for htmx, and I'm adding a feature for returning oob partials. When returning the partials, I'm wrapping their template fragments in a 
    <div id="destinationId" hx-swap-oob="true">
    however, now there is an extra div and extra 
    id
    on the element. Is that a way to tell htmx to place the child element in the destination when doing the swapping and dropping the wrapping div?
  • m
    out of band swaps are 
    outerHTML
    by default, so you shouldn't need a wrapping div: you should be able to just put the ID on the target and call it good. You can use more elaborate values for 
    hx-swap-oob
    as outlined here: https://htmx.org/attributes/hx-swap-oob/ * 
    true
    * any valid 
    hx-swap
    value (e.g. 
    innerHTML
    ) * any valid 
    hx-swap
    value followed by a colon, followed by a css selector
  • s
    The colon hx-swap selects the target, right? It doesn't allow for unwrapping the payload. I'm only wrapping the oob to add the target and hx-swap-oob attribute. Perhaps I should not try to be too helpful in my processing...
  • b
    You're doing it right and there is no way to add the whole element on which you included hx-swap-oob to the document currently, it will be always unwrapped. I have a difference of opinion about it too, but it's a small annoyance at the end of the day. One way I cope with it is the thought that something ending up in the DOM with the hx-swap-oob attribute would be weird.
  • s
    I've removed the wrapping. I'm OK with the current implementation, just wanted to ensure I wasn't overlooking something obvious. I'm also OK with the 
    hx-swap-oob
    attribute appearing in the DOM since it is a breadcrumb indicating that the contents were pushed into the dom from a response versus an `hx-get`/`hx-trigger` showing how something got pulled in.
  • e
    How can I prevent a ws send? The seemingly obvious thing, i.e. 
    <a _="on click halt" hx-ws="send" ...
    doesn't prevent the send.
  • e
    (ofc the real usage would involve a conditional)
  • m
    I would flip it an use an explicit 
    hx-trigger
    with a custom event that you fire. I suspect there is an event listener ordering issue, w/ the hyperscript listener firing after the htmx listener has been added.
  • e
    Yup, that works
  • e
    I do dearly still wish for an idempotent swapping method, that's what I'm working around the absence of with the ws send prevention
  • c
    Afternoon<
  • c
    Im using DataTables, and once the data is loaded the tables clear
  • c
    apparantly htmx.process() needs to go somewhere?
  • c
    If so not sure where to put it
  • b
    I'm not familiar with DataTables. I assume there is something like an async 
    load
    method that puts everything in the DOM? Then htmx.process(myTable) should go after that
  • c
    The only code there is htmx.onLoad( function () { $('#data-table').DataTable(); });
  • c
    on the table is hx-get to get the rows
  • m
    Anyone got experience with HTMX and LeafletJS?
  • m
    Solved it myself, seems a little wierd but that might be the Django package
  • l
    I try hx-push-url="false" on a , within a hx-boost context. It has no effect. Sending a HX-Push: false in the response however works (as in: no url is pushed). I'd rather have it the html though - any ideas what I am missing?
  • l
    a hx-target on the works, btw.
  • g
    I think boost is its own shortcut and a drop in replacement for a regular anchor tag. If you don’t want the URL to change, just substitute hx-get for the href and it should work just fine 😀
  • g
    Hx-boost is a great “gateway drug” into htmx, but pretty soon you’ll want to replace all your needs with hx-gets and hx-posts. That’s how addiction works 😉
  • w
    This might be a firefox thing, but I've noticed if I don't use a 
    href
    in the 
    a
    tag then the cursor doesn't change on hover.
1...684685686...1146Latest