https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    how could body be null?
  • b
    No idea 🙂
  • m
    me neither
  • b
    huh, if I put hx-history-elt on the main div, it seems to work
  • b
    Omitting it def makes it blow up. Interesting.
  • b
    If I have time tomorrow I’ll try and put a simple repro together.
  • m
    roger roger
  • b
    Does this combobox demo work for anyone? It doesn't seem to work for me (Firefox on Fedora) https://benpate.github.io/hyperscript-widgets/combobox/
  • t
    Nope, getting a whole bunch of CSP errors
  • b
    Ha, I figured it out. For some reason htmx and browser-sync don't play nice together
  • b
    Are components a thing? Is there a guide on how to get some form of reusability?
  • b
  • h
    ive come across a situation where im swapping in a new fragment oob but none of the hx triggers are firing on the swapped in content.. console doesnt show any action and no requests are being made - any ideas?
  • h
    it works fine on a full page refresh when the updated fragment is loaded inline
  • h
    solved, swapped in fragment didnt reference the url properly. user error strikes again
  • m
    is there a way to swap in just attributes from a hx-swap-oob, eg. add a class to an existing element?
  • m
    not currently, although the morph extension does this to an extent
  • f
    I'm using 
    hx-history="false"
    directive on one of my elements and when I click browser back it retrieves page elements from the server and not from the 
    htmx-history-cache
    . I've also noticed that when htmx loads history from the server it adds the header 
    HX-History-Restore-Request
    around which I've built a custom logic that adds a response header 
    HX-Location
    but this response is not handled by the htmx. I've taken some time and did some research on htmx source code and I found that 
    loadHistoryFromServer
    function doesn't check for response headers at all. I can understand why, but still wonder if was there any particular reason to handle 
    XMLHttpRequest
    differently than 
    handleAjaxResponse
    function for instance?
  • b
    so apparently webkit is adding support for "declarative shadow dom", https://webkit.org/blog/13851/declarative-shadow-dom/ which lets you use shadow dom without js. ( https://webkit.org/blog/4096/introducing-shadow-dom-api/ ) I'm honestly very familiar with these features, but it seems like there could be some interesting overlap with htmx... thoughts?
  • b
    Copy code
    html
<button hx-post="/endpoint" id="myid1" hx-target="#result-div1" type="button">
<button hx-post="/endpoint" id="myid2" hx-target="#result-div2" type="button">
    Is there a way to get the value of the id that triggered an HTMX event?
  • b
    Probably the simplest way is to add a query parameter to distinguish them on the backend:
    Copy code
    <button hx-post="/endpoint?id=myid1" id="myid1" hx-target="#result-div1" type="button">
<button hx-post="/endpoint?id=myid2" id="myid2" hx-target="#result-div2" type="button">
    But maybe you don't want that solution and you have a good reason for making things more complicated, in that case there also hx-include https://htmx.org/attributes/hx-include/
  • b
    Going with the first option, how may I access the id in 
    htmx:responseError
    event?
  • m
    htmx will include the ID of the triggered element in the 
    HX-Trigger
    request header (not to be confused w/ the 
    HX-Trigger
    response header, which triggers an event)
  • b
    can I access this value in 
    htmx:responseError
    ? My 
    evt.detail.triggeringEvent
    doesnt show this value
  • m
    oh, I thought you wanted this server side
  • m
    lemme look at the code, one sec
  • m
    looks like you do have the target
  • m
    is that enough?
  • b
    evt.target.id
  • e
    @mysterious-toddler-20573 not sure if you saw my ping the other day or my PR, but I wanted to make sure it's on your radar: https://github.com/bigskysoftware/htmx/pull/1250
1...101810191020...1146Latest