https://htmx.org logo
Powered by
# htmx-general
  • b
    Agreed that we need Carson's input here 🙂
  • a
    Hmmm... I think I may be at least partially incorrect here. I think 
    HX-Trigger
    and `HX-Trigger-Name`are actually the equivalents of the Intercooler 
    ic-element-id
    and 
    ic-element-name
    parameters I was referring to earlier. These have not been removed and will still be sent... which means the use case I mentioned will work just fine.
  • a
    Oh man..I might have this all wrong. Looking at it again now, it seems that it might be mapped like this, i.t.o. Intercooler -> htmx equivalent functionality: 
    ic-element-id
    -> 
    HX-Active-Element
    and 
    ic-element-name
    -> 
    HX-Active-Element-Name
    , along with 
    ic-trigger-id
    -> 
    HX-Trigger
    and 
    ic-trigger-name
    -> 
    HX-Trigger-Name
    . If this is true, then my original statement holds, which is to say you won't know server-side which submit button in a form caused a hx-post, for example.
  • a
    But, now I'm just gonna sit down and shut up until Carson come and sets me straight 🙈😅
  • a
    To clarify my understanding, I just added this section to Intercooler migration guide I'm busy drafting. It would be great if someone could confirm that these mappings are correct, as it stands currently:
  • m
    OK, I'll just have a look at what's going on in htmx-general...
  • m
  • m
    OK so
  • m
    the reason for the removal of those headers is that the caching only treats requests with the same headers as being equivalent
  • m
    so if a header changes, the cache will be ignored (is my understanding)
  • m
  • b
    Is that necessarily a bad thing?
  • m
    Well, if you want the prefetch and an actual click to use the same cache, you need them to have the same headers
  • m
    So I took out some less important header that could change between them
  • m
    in particular, 
    getDocument().activeElement
    could change on the click
  • b
    How so?
  • m
    the active element on hover is, say, the body, and then it becomes the link
  • m
    similarly, the event target could change
  • m
    all of those were what I considered "nice to haves" but not crucial, but I can document how to readd them via javascript & hyperscript
  • m
    HX-Trigger
    is the ID of the triggering element, which remains stable and is still included
  • b
    Ok, makes sense for the most part. What about 
    HX-Current-URL
    ?
  • m
    I can see readding that, perhaps I was being a bit too american aggressive
  • b
    Glad I can bring the european skepticism to the table 😉
  • a
    Well, glad I wasn't the only South African confused one 😁
  • b
    You call that a changelog? This is a changelog...
  • m
    if only you were a contributor with access to the repository...
  • m
    alas
  • a
    Apparently also:
  • m
    all future htmx changelog entries:
  • a
    Sorry, my bad. I had a typo before:
1...120121122...1146Latest