https://htmx.org logo
Powered by
# htmx-general
  • h
    both of libraries are a little out of date
  • h
    and I think the missing chunk before was the frontend ease of use - what was the point of having a template partial outside of a page refresh if you weren't really using partials/writing a bunch of jquery
  • h
    I think what I'm really excited to think through at some point is what django template tags could make life easier for writing out htmx tags
  • f
    Ah, I had tried it a few different ways but settled on the button. I'll try moving everything to the form tag and seeing how it is. I suppose in an ideal world I wouldn't even need to extra form tag, but it seems tidier (and can fall back and work without htmx/js). I'll try that out
  • w
    Accidentally posted in #796428329531605032 about FontAwesome icons blinking during HTMX submit. It was recommended I look into the settle delay, doing that now.
  • w
    @User If I want to change settle delay to zero, do I just add
    Copy code
    <script>
  htmx.config.defaultSettleDelay = 0
</script>
    after I import htmx? or is there another way?
  • a
    You can also set it in a meta tag
  • a
    This is at the bottom of this page: https://htmx.org/docs/#config
  • w
    Still happening with a zero settle delay. I should note that it's all icons, even those outside of the HTMX target area.
  • a
    🤔
  • a
    Then I’m a bit stumped, sorry
  • a
    Can you try and reproduce it in a minimal example?
  • w
    I think I might try using Bootstrap icons and see if it still happens
  • w
    Yeah, I'll try to put together an example
  • a
    I really doubt if it’s because of fontawesome
  • a
    Are you perhaps reloading the font awesome css file every time?
  • w
    I don't think so, since I have my headers, hav, footers, etc excluded from HTMX requests based on the way my templates are set up. Working on making a reproducable example
  • w
    Well, good news is it doesn't seem to be an HTMX issue, since my barebones example didn't recreate it. Might look into if it's somehow reloading FontAwesome css (although examining DevTools with the bug tells me the only request made is an HTMX one)
  • a
    Are you returning a fragment in the htmx call response? Or the whole page? Although, if if it's the whole page, theoretically only the body should get replaced anyway
  • w
    Fragment. I'm noticing it happens in my initial set up
    Copy code
    <div id="example">Initial Content</div>
<form
  hx-get="/"
  hx-target="#example"
  hx-swap="innerHTML"
>
  [stuff]
  <button>
    <i class="fa fa-fw fa-download"></i>
  </button>
</form>
    but it doesn't happen when I ditch the form and I put the HTMX on the 
    button
    tag
  • w
    Also *doesn't * happen if I move the button outside of the form (and keep the HTMX on the form, but specify
    Copy code
    <button form="#form" type="submit"></button>
  • a
    🤔
  • a
    The fact that the fa-download icon on the button blinks during reload, tells me it somehow has to have to do with the content swapping. I would have said it's the settle delay, but you say you've set it to zero? This is what our meta tag looks like for reference:
    Copy code
    html
<meta name="htmx-config" content='{"defaultSettleDelay":"0ms"}'>
  • a
    Although you also said it happens on icons outside of the swap target?
  • w
    Yeah, the default value was 20ms btw, but I set it to zero. I think I've discovered the issue, it seems to be something with my bootstrap scss. Will post when I know more.
  • w
    Yup, it only happens when I include my 
    custom.scss
    , which imports bootstrap5 scss and changes some colors etc. When I just include the standard bootstrap.scss everything works fine (I'm using a 
    django-sass-processor
    in my django template). I'll try to dig in a bit deeper and see if I can figure out exactly why this is, but it seems to be quite outside the realm of HTMX's fault.
  • w
    It's strange because the 
    <head>
    (where the link to the css is located) is not refreshed in the HTMX call
  • a
    Oh, I forgot that the default settle delay was dropped to 20ms at some point … it used to be 100ms. But yes, I’ve often run into similar things where I think it’s htmx misbehaving when in fact it’s my code doing some stupid thing.
  • w
    ugh eff me. I forgot that at one point I had added this to the css
    Copy code
    .htmx-request button i:not(.htmx-indicator) {
      display: none;
    }
    🙄
  • w
    sorry for the wasted time 😐
1...513514515...1146Latest