https://htmx.org logo
Powered by
# htmx-general
  • b
    The "Bringing back classic" category
  • m
    On a history miss I assume that the entire page would need to be replaced. But I think some headers makes sense.
  • m
    HiFi frameworks - HTML is Fine
  • s
    I would generally want a full reload on history miss but as far as I can tell htmx calls the url without hx headers but then only swaps the inner html of the target element. in this case I specifically target a div
  • m
    ugh, that sounds wrong
  • s
    a full refresh that just navigated to the page would be fine
  • m
    It should pull down the content and swap it as innerHTML for the body
  • m
    :/
  • s
    or a call with hx header that swaps the target div, either option could be useful in some situations
  • s
    it does
  • s
    but I just target something other than body
  • s
    but innerhtml swap on body is != refresh
  • s
    so without hx headers
  • s
    its hard for the server to serve the proper data
  • s
    id really like to config full page refresh vs innerhtml swap on history miss in any case 🙂
  • s
    my use case is to avoid redrwaing the nav elements every page load, since the expensive part of this is all the auth checks in the server, having to return them on history miss isn't ideal.
  • s
    but its workable jsut fine, though in this case id rather just do a full navigation to the url as opposed to anything more clever.
  • s
    anyway, I love htmx, its just a minor nitpick 🙂
  • s
    if history miss includes hx headers then ill also be a happy camper, that is probably the more performant solution, assuming no strange breakage.
  • s
    my server code is roughly: if (hx headers present) return partial .. else return full page with layout.
  • s
    if that helps making sense of my rambling (im just excited about writing dynamic pages without having to learn a massive framework)
  • m
    🙂 I get it. I'll definitely include a header. And we should make the history aspect pluggable so you can do what you want
  • m
    Anyone know why 
    afterSettle
    gets triggered twice here?https://codepen.io/jreviews/pen/QWKYrbB
  • m
    i believe because it is an outerHTML target, so we trigger it on the original element as well as the new element
  • m
    Thanks. And the way to differentiate would be by looking at etv.target? I am actually having a related issue that I can't replicate on codepen. Similar example on Safari mobile produces the same two events, but evt.target is not null on either one.
  • m
    I don't think target would be null, but rather it would be the old content and then the new content.
  • m
    :/
  • m
    Annoying, sorry about this
  • m
    outerHTML is tricky
  • m
    This is evt.target and has different values depending on the browser. Weird.
1...132133134...1146Latest