https://htmx.org logo
Powered by
# htmx-general
  • m
    i really hate this stuff, but there's nothing stopping people
  • p
    Hmm and what can i do to fix it? im on localhost
  • h
    Right, last question for now, I don't want to monopolize: If I want to click a button and serve a file as an attachment, should I do that "outside" of htmx? Since usually this is not an AJAX request.
  • m
    yes, do that as a normal link: ajax won't download properly
  • m
    have you added any new libraries lately?
  • h
    Thanks Carson. Let me say I think you are onto something with this project. I hope htmx eventually becomes moot because it's in the html spec and browsers implement all this natively 🙂
  • m
    that would be a lot easier on me!
  • a
    You and me both! Because at that point Carson will get a knighthood (like Sir Tim Berners Lee) and then you and I can go around and tell people, "yeah, we knew him from way back before he was famous". I fear you and I may die of old age before they get around to extending the html spec like that though 😅
  • h
    Is it possible to assign the value of hx-get via javascript variable?
  • b
    I would start by searching my entire codebase (including lib source) for the string 
    history =
    , but I'm a barbarian like that
  • b
    Do you mean to "bind" the value of 
    hx-get
    to the value of a variable? Or simply set 
    hx-get
    programattically?
  • a
    afaik no (?). I used hyperscript fetch for the cases where I dynamically needed to build up the url client-side
  • a
    Now that I say that... I wonder if one could change the value of the hx-get attribute via script (JS/hyperscript/whatever) and the call htmx.process() on the element again?
  • h
    Set it with a Javascript variable programmatically.
  • h
    Trying with Alpinejs at $data at the moment.
  • a
    I suspect you'll have to call htmx.process() as well afterwards ... 'cause htmx reads the value of hx-get when the page / element loads initially, afaik. I am not 100% certain on of any of this though, so if you get it working some other way, please let us know 🙏e
  • h
    Ok thanks. Will do! 🙏
  • h
    @User @User Found it with Alpinejs x-bind directive:
    Copy code
    <a x-data="{url: '/fund/'+fund.id}" x-bind:hx-get="url">
    <span x-text="fund.title"></span>
</a>
  • a
    And that works? Hey hey! 👊
  • h
    👊
  • a
    Now you gonna make me go back and re-evaluate a whole bunch of life choices @User 😁 👍
  • h
  • h
    Been porting an Ember, Django REST framework solution to Django templates, HTMX and Alpinejs for two months now. Going slowly but surely.
  • a
    Hey @User htmx 1.7.0 is shouting at me for a selector used in 
    hx-include
    that returns no matches on page load. Thing is, that selector points at... nothing initially, because the dom element(s) it points at, gets created by a JS widget later on. By the time the htmx request is made (user selects an option from a dropdown), the elements are there and get included correctly in the request and everything works just fine... but I've got a browser console that's redder then me on my 1st day on the beach after winter. Any ideas, besides just ignoring my angry console?
  • a
    Btw, I'm pretty sure that's what it is, because htmx is very specific in its wrath:
  • h
    yeah that's neat and the other neat alpine combo is
  • h
    @htmx:before-request="alert('foo')"
  • m
    🤔
  • m
    maybe we shouldn't log an error there
  • m
    yours is a reasonable case
1...591592593...1146Latest