https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • l
    That is very exciting. Thank you!
  • m
    yep, no prob
  • c
    Has anyone implemented htmx with ColdBox ( https://coldbox.ortusbooks.com/ )?
  • g
    Howdy @User -- I think there are lots of backends represented here. The biggest selling point of HTMX (for me) is that it's pretty agnostic in terms of the server. Any HTML server should be able to work with HTMX right out of the box.
  • g
    One "server integration" issue that's come up is listening to HTTP headers to switch between rendering a full page or a partial page. That might be one area to dig into ColdBox to see how you'd accomplish that.
  • l
    From a quick look at the docs for coldbox (https://coldbox.ortusbooks.com/digging-deeper/recipes/building-rest-apis#security) looks like getting access to headers isn't an issue with something like
    Copy code
    event.getHTTPHeader();
  • c
    Future reference for those combining ColdBox with htmx, RenderData() ( https://coldbox.ortusbooks.com/digging-deeper/coldbox-proxy/the-event-handlers/renderdata ) was the key for rendering the model/entity/query to the proper html format utilizing the Value Select example ( https://htmx.org/examples/value-select/ ). I look forward to implementing htmx throughout my code. Thank you!
  • b
    Anyone else able to confirm this bug? https://github.com/bigskysoftware/htmx/issues/228
  • g
    It got real quiet in here as soon as @User asked us to confirm a bug 😉
  • g
    Sorry, Ben. I have been trying to keep this kind of super-dynamic code out of my project, so I haven't run in to anything like it.
  • b
    No worries, confirmed it with a test 😉 https://github.com/bigskysoftware/htmx/pull/229
  • g
    Cool . Glad you could confirm it, at least 🙂 There was a request/report a while back about trying to delay execution of scripts until the new DOM nodes had settled. I don't know if this is related, but they're close enough that it's worth considering.
  • m
    Yeah, it's a problem with the way that HTML parsing works
  • m
  • m
    We have to do some jankyness with some types of tags to get the DOMParser() to parse them correctly
  • m
    unfortunately, if a tag is the first tag, for whatever reason the DOM parser ignores it
  • m
    I may wrap everything in a div always, but that seems like it might have side effects too
  • m
    so you want to work on an open source project...
  • b
    ...it’ll be fun...
  • e
    hello all , is there a way to break out of the hx-boost functionality in a child element eg a href
  • e
    im thinking in terms of a hx-no-boost kind of funtionality
  • m
    hx-boost="false" should work and disable it for all child elements as well
  • e
    > hx-boost="false" should work and disable it for all child elements as well @User thanks - 👍
  • n
    HTMX got briefly mentioned on the Stack Overflow Podcast https://pca.st/diid9cbr#t=2m28s
  • u
    Heyo! I have a bit of a problem handling history on my site. What does 
    historyCacheMiss
    mean or what causes it? I have a container with 
    hx-history-elt
    and bunch of links that have that element as the 
    hx-target
    but for some reason back button breaks the site. 🤔
  • b
    Thanks for sharing @User!!
  • m
    hx-history-elt is the element to take history snapshots of. Typically you do not need to use this attribute, since it will by default use the body, which works well in most cases. It doesn't have any interaction with the targeting mechanism directly, so you should just target whatever makes logical sense and let the default do its thing
  • m
    @User ☝️
  • u
    Ok. I just assumed since I only want every interaction to change what's inside the container and ignore the rest (navi & a chat service which is loaded from a script) that I should use that as the history snapshot.
  • u
    But I think the history is broken even without the 
    hx-history-elt
    . I think we're doing something silly atm. Tried to debug it for a few days but couldn't get it working correctly. 😆
1...697071...1146Latest