https://htmx.org logo
Powered by
# htmx-general
  • r
    gotcha, that does seem like it would work
  • m
    Yeah, if you are willing to do the work the "right right" thing is to uninitialize the js on the way into the history cache
  • m
    Some libraries have a way to do this, but not all. Basically look for a mechanism to undo the DOM manipulation. I wonder if we should snapshot before we trigger the 
    ready
    stuff. That would be cleaner.
  • m
    that's an interesting approach to think about: allowing you to configure when a history snapshot occurs.
  • m
    history is such a PITA
  • w
    Well, I do know I have to reinitialize bootstrap tooltips and popovers in JS using an 
    htmx.onLoad()
    js call, so I thought maybe re-initializing the dropdowns would work, not sure yet tho EDIT: This doesn't seem to work, which is strange to me
  • w
    Am I reading the docs correctly? If I set 
    hx-push-url
    to False, will History support be disabled? Is it possible to set 
    hx-boost="true"
    and 
    hx-push-url="false"
    together?
  • m
    I think what you want is to disable the history cache
  • m
    you can set its size to 0
  • w
    Gotcha, will try EDIT: Still doesn't seem to fix the dropdown issues 🙄 Will mess around somemore
  • m
    huh
  • m
    we should be fully retrieving the HTML from the server in that case
  • m
    that almost always fixes history related stuff 😑
  • w
    I just removed htmx.js to verify it's not some other issues, and clicking back resulted in working dropdowns, so yeah -_-
  • w
    Setting 
    '{"historyEnabled": false}'
    in a meta tag broke all sorts of things, so I suppose having that enabled but setting 
    historyCacheSize
    should have been a winning solution
  • m
    yeah, htmx.config.historyCacheSize set to 0 is the "fix"
  • w
    Just verified in console that it was set to zero. Now when I click "back" I do see an XHR GET request for the page, but the dropdown still doesn't work 🙄 Maybe I should just use hyperscript to toggle them
  • m
    wtf
  • w
    Trying to think, is this something I could reproduce using the new sandbox thing? Not sure how browser back requests work in there
  • w
    Well, strangely enough I think this might be more of a weird bootstrap 5 thing than an HTMX thing. It looks like the dropdown trigger elements don't have events associated with them. Other bootstrap components, like tooltips and tabs, show associated 
    event
    in debug console and they work fine when using browser "back." However, the dropdowns, even when they do work properly (i.e., in normal browsing and not pressing "back") do not show an associated 
    event
    in browser tools, so I suppose Bootstrap has some other method for determining clicks (I just noticed that there are a lot of event listeners on the 
    <html>
    tag that come from 
    bootstrap/js/src/dom/event_listener.js
    ).
  • w
    @User So, it looks like it was because I was loading my js lib at the bottom of the 
    <body>
    . So "going back" apparently made them load multiple times, or at least repeat event listeners (I noticed hyperscript was also doubling behaviors), so it wasn't that Dropdowns weren't working, but that they were getting fired twice. I suppose loading JS libs in the head is the solution, but I always heard it was best to load them last. I don't think it's a huge deal to load them in the header, but just wondered what your thoughts were. EDIT: So, I went ahead and removed the 
    historyCacheSize: 0
    config and things still work as they should
  • g
    How do I nest HTMX ?
  • g
    So if I have a change event that inserts HTML, and I have another form with HTMX in that inserted HTML
  • g
    It should just work.
  • g
    Any html that’s loaded by htmx will be scanned when it’s loaded in.
  • g
    If you manipulate the DOM outside of htmx, then you need to call 
    htmx.process()
    on the new nodes so they htmx knows about them.
  • g
    Does this answer your question?
  • g
    Yeah, it might be because I have some tweaks going on to accommodate select 2
  • g
    @User Would this be a circumstance where process() would be needed ?
  • g
    You’re adding stuff to the DOM outside of htmx. If it has htmx tags in it, then yes.
1...603604605...1146Latest