https://htmx.org logo
Powered by
# htmx-general
  • g
    Plus, it’s written very conservatively right now, so the preload is not applied unless you explicitly put a preload attribute on the element. So you’ve really chosen to do this.
  • m
    Ah
  • m
    YOU ASKED FOR THIS
  • g
    This.
  • m
    OK, so the problem is that the request needs to include the pre-request logic from htmx core
  • g
    Yes please.
  • g
    Access to the built-in xhr function would address it.
  • m
    but you need a no-op 
    xhr.onload
  • g
    Yes. I’d assume the function we publish would accept a callback (or promise, or whatever). From this extension, we’d just pass an empty function.
  • m
    OK
  • m
    i need to look at that method and think
  • g
    Yup. I think it will be a little painful, but a good step forward.
  • m
    proposed sig:
    Copy code
    js
  htmx.ajax(verb, path, [elt default: body], [onload default: normal swap algorithm])
  • m
    Copy code
    js
  htmx.ajax('GET', "/foo")
  • g
    Thank you for your attention on this 🙂 What function would 
    elt
    support?
  • m
    or, for this use case
  • m
    Copy code
    js
  htmx.ajax('GET', "/foo", theEltWeArePreloadingFor, function(){ /* do nothing, cache result */ } )
  • g
    Is this because there are a bunch of attributes on the element that will need to be included in the request?
  • m
    yes
  • g
    (damn)
  • m
    we need to collect any variables, etc.
  • m
    header, any event processing, etc.
  • m
    I think we need the whole shebang
  • g
    Yes, I agree with the whole shebang.
  • g
    Now that we're here, for this use case it would be good if we DIDN'T process the response headers. 
    HX-Push
    , 
    HX-Redirect
    , 
    HX-Refresh
    would all cause havoc if we're preloading page fragments. I may have asked for more than I bargained for.
  • g
    An alternative might be to fake the 
    HX-Request
    header into my extension code, but that feels even more icky.
  • m
    Yes, of course
  • m
    With the empty onload handler, you would ignore all that
  • m
    You'd get everything except the response handling, which I think is the right thing (ish)
  • m
    does the http cache take request headers into consideration?
1...109110111...1146Latest