https://htmx.org logo
Powered by
# htmx-general
  • m
    looks like we do exclude disabled inputs. That seems wrong if that's now how HTML normally works
  • m
    it also seems likely to break peoples code if we change it
  • m
    😑
  • g
    Not a huge deal on my end. Sometimes you like to show and control what is passed through a form, but there are other ways to accomplish that
  • s
    hi everyone how can i resolve this issue. i have an item in the cart and i am using htmx to rerender the cart each time the counter increment/decrement button is clicked using hx-target and hx-swap. but when i click on any of this button for the initial time, the content increases in the dom but doesnt rerender unless i click the second time. that is if i had one item added in the cart (1) and click the increment icon it increases in the dom but doesnt render but when i click the second time it will now rerender with a value of 3 and then starts working as it should. so what can i do to solve this
  • p
    Took me a while to get my head around this stuff too. HTMX is for server interaction. Use Alpine, Hyperscript, or even vanilla JS to do client side DOM manipulation which doesn't require a trip to the server. Alpine is great by the way, and plays quite nicely with HTMX. For server stuff, you use 
    hx-something
    attrs. For client-side (Alpine) stuff, you use 
    x-something
    attrs.
  • b
    Hi! I'm newbie with htmx, trying to implement boosting to the entire project just adding hx-boost to the body. All is going as expected but I can't figure out how to disinherit boosting to specific elements, like image links and other custom conditions?
  • m
    hx-boost='false'
  • m
    just realized we have terrible documentation on this 😑
  • b
    It's OK, but I'm talking about dynamically added content. I can make regex added this attr serverside, but it's looking weird
  • m
    Generally the config "cascade" is broken by `hx-disable`… but maybe that still doesn't fit your pattern?
  • b
    In my case, I have WordPress based infinite news timeline. Each article can contain different type of links: external, internal either internal _blank either linked with pics (I'm willing to open them in some lightbox solution). So the serverside parsing content matching this conditions and marks that links with hx-disable attr looking really weird solution, so I'm trying to figure out more proper way to achieve needed behavior
  • s
    okay, just download some alpine.js tutorials
  • g
    it's always fun when you go to link the docs and the docs aren't there
  • b
    Yeah, programmers really knows what the 'fun' is
  • b
    So there is no some "filter" over hx-boost directive, that I can modify through plain js?
  • m
    the htmx way would be to generate the 
    hx-boost='false'
    attribute server side, lemme take a look at the code and see if there's an alternative
  • m
    nope, we don't currently trigger an event on the boosted element
  • m
    we could, interested in forking and adding it?
  • b
    I think it's necessary to have such functionality more flexible with custom hooks like triggering events or global config modifications. Shy, I'm not good with a Git still for making forks and PR's, but as far as I go, I plan to promote htmx based solutions within WordPress, cuz htmx is the first tech, that ideally fits the WP workflow without any special conditions
  • h
    I would like an event on boosting
  • h
    I've been thinking about doing that
  • h
    it would be useful for a lot of js libs to init/gc
  • b
    I think global config param will be useful too. Like htmx.config.boostExclude = '[target="_blank"], [href$=. jpg], #etc *'
  • p
    Keep it as a breaking change for 2.0?
  • h
    imho trigger an event and let the event cancel the boost ala preventing an htmx swap
  • m
    yep, that's the way
  • p
    will there be an upgrade path for HTMX 2.0? 🤔
  • p
    or if the breaking changes will be too much.
  • p
    the project is still evolving so I wont be surprised.
1...650651652...1146Latest