https://htmx.org logo
Powered by
# htmx-general
  • m
    yeah, just a github issue is fine
  • h
    k - I think the situation would be if you boost true somewhere and boost false somewhere else
  • h
    I might try to make a failing test
  • m
    ah, right, no this is fine
  • m
    basically we look in the whole doc to see if there are any boost tags, because a parent 
    hx-boost
    would effect the new content
  • h
    For this boosted redirect thing - everything around boosting is very elt focused - I'm thinking of making a fake a tag, putting boost on it and then simulating a click - do you know any JS that will perform the click without actually bubbling the event up
  • m
    it's a perf hack: we don't include the boost processing logic unless there's a chance that the content was boosted. And the only way it could possibly be boosted is if somewhere in the DOM there's an 
    hx-boost
  • m
    right, coming back, the logic here is right, just looks a little strange.
  • h
    ic
  • h
    and just including it doesn't mean it'll be called
  • h
    but don't include if no chance it'll be activated
  • m
    basically: we only want to include the 
    a, form
    selectors if and only if there is a chance they could be boosted.
  • m
    iirc someone complained about having like 50k anchors and this taking forever even though they weren't boosted
  • h
    yeah makes sense
  • m
    does it really, tho?
  • h
    with explanation 🙂
  • h
    I might put a comment in there/rename the function
  • h
    isChanceOfBoosting or something
  • m
    good idea u just 7 🐝 'd yourself
  • h
    o7
  • h
  • h
    I gotta run to dinner but this is what I'm thinking for the boost-redirect stuff I was talking about: https://github.com/bigskysoftware/htmx/pull/832/files
  • h
    if that looks good I'll add tests + docs over the next couple of days
  • r
    tbh with an acyonym like "howl" I'm surprised the furries haven't taken over the server yet.
  • b
    Any particular reason why the htmx.process function would fail to process elements? I have a div that is loaded asynchronously with ajax and js. I added an hx-get to it and after the div is loaded i call htmx.process in a script element just underneath it. For some reason this seems to fail now and the div is missing the event listener completelly
  • m
    Can you load up the uncompressed version and debug it? No reason this shouldn’t work.
  • b
    I'm trying that out but not too knowledgeable of javascript, was hoping to be able to avoid doing that
  • b
    Funny thing is the same procedure works in diifferent element load so something is up
  • e
    GM. Is there any way to use hx-select to select/replace more than one node in the DOM ?
  • e
    This because I do not control the HTML I want to include. I mean cannot easily tune it.
1...581582583...1146Latest