https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • c
    Thanks
  • r
    hx-push-url
    doesn't work well with `loading-states`: if I go backwards (push back button) all elements with 
    data-loading-disable
    become disabled I assume it's because 
    loading-states
    first adds disabled attribute and only then 
    hx-push-url
    captures current DOM (together with disabled attribute) what do you suggest to do in this case?
  • r
    As a workaround, I suggest to try 
    data-loading-delay
    attribute with a tiny value (like 5 or maybe even less)
  • r
    this attribute is inherited so you can put it on 
    body
  • r
    yeah, works now, thanks. Just have to set delay to ~100ms, otherwise sometimes it's still disabled
  • r
    Great!
  • r
    still, I imagine such edge case should be considered as a bug? 🙂
  • f
    Not that I know of but you can save and restore it like this in a contentEditable, but it makes only sense if the content doesn't change http://jsfiddle.net/6jbwet9q/9/ This works if you sync the contents of a contentEditable with an input. The sync is what I did here https://discord.com/channels/725789699527933952/909436816388669530/1024267243065987123
  • r
  • r
    cool
  • m
    it sounds like the loading-states extension needs to properly clean out the DOM before it is persisted to the history cache
  • m
    I'll try to find the dev and let them know
  • m
    all the major morphing plugins should keep the caret postion, etc. if you keep the id stable
  • r
    The extension should hook into a different event. Currently it performs cleanup on 
    htmx:afterOnLoad
    which happens after response is processed (including interactions with history api). Probably, should have used 
    htmx:beforeOnLoad
    instead
  • r
    just tested this, yap works
  • r
    Did you edit extension source code?
  • r
    If so, nice!
  • r
    PR welcome, when (and if) you have time
  • r
    yes 🙂
  • r
    changed 
    htmx:afterOnLoad
    to 
    htmx:beforeOnLoad
    🙂
  • r
    obviously I have no idea if any other problem could happen because of this
  • r
    Still, this is great news
  • r
    thanks!
  • w
    Is it possible to use HX-Location and and HX-Push-Url=False together? I'm not sure if my headers are correct or if it's just not supported
  • m
  • g
    Hi. Does anyone have a getting started guide for when working with WordPress? For example, click on a button on Page A to load the content of #my-element on Page B in Page A.
  • r
    1. If you want to just load entire pages, use boosting 2. If you want partial updates, use hx-target with hx-select in various proportions
  • p
    This element selects the whole value upon focus via AlpineJS and gets swapped with itself once the backend processed the changed value: 
    <input type="text" id="stable" @focus="$event.target.select()" hx-post="" hx-trigger="blur">
    The selection state is not preserved. It only works when this snippet is used: https://github.com/bigskysoftware/htmx/issues/343#issue-796944483
  • r
    what swapping extension do you use currently (if any)?
  • p
    I did not specify one specifically. This is on htmx 1.8.2.
1...885886887...1146Latest