https://htmx.org logo
Powered by
# htmx-general
  • m
    needs more docs (sorry @User)
  • e
    (I'm simulating it in a spot that has keyboard shortcuts and hitting the keys for multiple things at once lol)
  • e
    Bingo! I've got another spot that has mouse-overs to trigger hx events. If I mouse over multiple of those at once, it causes the error.
  • e
    Is there an ETA on when that feature will release?
  • m
    i am hoping to have 1.7 released end of the month
  • e
    This PR adds more examples for it: https://github.com/bigskysoftware/htmx/pull/804
  • m
    absolute kings helping me even keep track of my own damned project
  • m
    if you are brave (and if you don't use web sockets or sse) you can try running against the dev version and see if you can use hx-sync effectively
  • e
    Hmm. I can try that. That'll give me a jump-start on the fix I'll have to implement in a few weeks anyways haha
  • e
    How do I import the dev version? 🤔 I'm using npm to import. So I suppose I could pull down the 
    master
    version and point to a local copy of the file?
  • m
  • m
    you can also just link that, if you trust github (I don't)
  • w
    I had to use 
    <script src="https://cdn.jsdelivr.net/gh/bigskysoftware/htmx@dev/src/htmx.js"></script>
    to get dev from GH, just FYI. I think GH serves the file with a MIME type that prevents it from being run from 
    <script>
    tags
  • m
    interesting
  • e
    Confirmed: that fixes it. Thanks! I'll be looking forward to the next release 😁 Keep up the great work on this library, btw!
  • g
    Thanks Rashad. Yes, I was able to create a link that would fetch html for prior step with the previously filled form values. However, if the user uses the browser back button can't do that, and what you get is an empty form, erasing prior form entries when used. This is not workable in current app because there are about a dozen form fields that need to be available when a user navigates back.
  • a
    You just made me realize that we’re also getting this… I’ve been wondering what was causing those undefined errors we see in the logs. Thanks!🙏
  • e
    Hmmmm. Is the code publicly available online? I can check it out when I get a chance
  • m
  • g
    my university has a sap-based app and i do say "they really should've used htmx" quite often
  • g
    I will put an example up. I just tried a work around using multiple divs on same page, without replacing the same target on each, but it has same behavior.
  • g
    This is a showstopper issue for me, back button support and not erasing entered form data is important for most apps I build. I hope it's my mis-use of htmx.
  • m
    Has the data been persisted to the server?
  • m
    If so set the history cache size to 0
  • m
  • m
    See if that fixes things
  • g
    htmx.config.historyCacheSize is set to 10, checked in js console.
  • m
    Can you set it to 0
  • g
    So empty form returned to user, user fills it out then makes request to server, server stores the data and returns the htmx partial response response and hx-push header, page is updated with response, and address bar is pushed. All great. Until the user presses the browser back button, no other request is made to server, and the prior page address & form are then current page, but it's empty.
  • g
    No effect.
1...563564565...1146Latest