https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • f
    My project is very much a framework at the moment, but I've got some cunning ideas to make it look more like a library and give back a feeling of freedom to the user.... the more library-like it is, the more it feels like people will be able to incorporate it into their solution without it getting in the way.
  • b
    I can't argue with that. For example for PHP world I'm sure Symfony's dicision on Stimulus and https://github.com/symfony/ux is well investigated. I've just said, I could not reach my goals with it, but it's absolutly about my use cases and my small-scale one-man-show hobby projects.
  • s
    Is there something in htmx like [up-expand] in unpoly? Add an [up-expand] attribute to any element to enlarge the click area of a descendant link.
    Copy code
    <div class="notification" up-expand>
  Record was saved!
  <a href="/records">Close</a>
</div>
    . See https://unpoly.com/up-expand
  • l
    @User There's an inherent scope question here. Does 
    up-expand
    involve interacting with the server? or is it specialized behaviors local only to the browser?
  • l
    I think, and @mysterious-toddler-20573 could correct me, that interactivity things (that don't involve client/server glue) are destined to be part of https://hyperscript.org so that there is a separation of concerns. That said, this line is hard to discover & cleanly articulate ...
  • m
    up-expand
    isn't needed in htmx, you would place the 
    hx-get
    on the parent element instead:
    Copy code
    html
<div class="notification" hx-get='/records'>
  Record was saved!
  <a>Close</a>
</div>
  • s
    Thank you for sharing your wisdom. Yes, you are right. up-expand is not about interacting with the server. Now I realized that the tag can contain everything (this was different in the past). The simple solution is to wrap the whole div in a .
  • l
    I think htmx semantics treat almost anything as an clickable element. You may not want the formatting that comes with ?
  • l
    I'm a newbie here, don't mistake my writing for wisdom
  • w
    Hi! I tried to return multiple elements with 
    hx-swap-oob="true"
    , but I get 
    htmx:swapError
    . What can cause this? Only one (top level) element can have the hx-swap-oob attribute? If not, could you please show me an example, where multiple elements are out of bound swapped?
  • w
    If I return only one element in the ajax response, then it works
  • m
    Right now hx-swap-oob must be on top level elements
  • m
    that's probably a bad limitation
  • m
    multiple top level oob elements should work, however
  • m
    unless there is a bug, which is impossible since I'm such a great programmer
  • m
    😑
  • w
    One of my elements is a 
    tr
    , the other one is a 
    span
    There must be a bug, because if I return only one, it works. But if I return both, then the result of makeFragment is nonsense
  • m
    Ah, yeah
  • w
    Both of them are top level elements
  • m
    trs are a nightmare
  • m
    we have special logic to make fragments work when you return a tr
  • m
    If you return the tr first, it might work
  • m
    :/
  • w
    Unfortunately, it does not :/
  • w
    By the way this is a great library. This is the only bug/problem I encountered so far 🙂
  • m
    OK, can you open a github issue on oob trs ?
  • w
    Sure, I will open an issue. But now, I have to find a workaround, because I have to finish this work by tomorrow. Maybe I split the responseText in two in selectAndSwap, and call makeFragment twice, or something
  • l
    @mysterious-toddler-20573 this is all due to quirks mode parsing and nonsense?
  • l
    There is "reparenting" logic for tr as I recall...
  • m
1...919293...1146Latest