https://htmx.org logo
Powered by
# htmx-general
  • w
    i believe it's along the lines of 
    on click put 'newValue' in my @value
    EDIT or 
    on click put 'newValue' in #myInputField's @value
  • m
  • m
    you can also drop the 
    @
    since 
    value
    is a property of the input
  • m
    General note: let's try to move hyperscript questions to #796428329531605032
  • s
    on message if its topic is _hyperscript send it to #hyperscript
  • b
    I was wondering if you could do something like:
    Copy code
    applescript
on htmx:afterSwap from #content
   if its elt is me
     toggle .a .b on #c
end
  • b
    (Excuse the wrong channel but I claim threading rights)
  • w
    I feel like it's acceptable since it's about HTMX events? 🤷 I like this solution, I'll try to implement it, thanks 🙂
  • b
    Is there an htmx+hyperscript playground anywhere? Or do any of the various fiddles support faking up some server responses?
  • b
    Feels like that would be useful
  • w
    This has come up before and I don't recall any great solutions. I found Mockjax, but didn't do any real deep diving into it
  • h
    I finally had a chance to read the sync document - what's the difference between dropping a synced element and aborting it
  • m
    we should create a jsfiddle or similar template
  • m
    does anyone know how to do that?
  • m
    one w/ htmx and hyperscript both installed
  • m
    and maybe an example implementation of an 
    hx-post
    or whatever
  • h
    is there a cdn link to htmx and hyperscript? that might be the simplest
  • w
    I feel like I'm going crazy: 1) I have CSS rules to make a form's submit button turn into a spinner when 
    .htmx-request
    is added to the form. 2) Manually adding the 
    hx-indicator="#my-form"
    attribute to the 
    form#my-form
    works properly: I can see the class get added in DevTools, and I see the spinner. 3) removing the 
    hx-indicator
    attribute (which according to docs should still add 
    .htmx-request
    to my form) breaks it, and the spinner doesn't show. but if I add 
    _="on submit log .htmx-request"
    to the form, the console shows 
    Object { _css: ".htmx-request", relativeToElement: form#my-form, escape: true }
    , so it seems like HTMX is adding the class even though 1) I can't see it in DevTools and 2) I don't get the spinner effect from my CSS (unless I'm misinterpreting this hyperscript output) Any ideas?
  • f
    Anything I'm missing here? 
    HX-Trigger
    response header doesn't seem to fire my 
    hx-trigger
    listener. Also tried registering the 
    hx-trigger
    without the 
    from:
    clause, but didn't change the behavior.
  • m
  • m
  • m
    see what's up
  • m
    I will take a look at this in a bit, my guess is that the 
    .htmx-request
    class is being added somewhere unexpected
  • w
    That was my thought, I was trying to figure out how to set up a listener to detect what elements .htmx-request is being added to (which was what I thought I was doing with the hyperscript, but perhaps some js in the console would be better, although I'm not familiar with MutationEvents (yet))
  • m
    you can load up the source raw, as above, and set some break points
  • m
    easy enough to find where the class is added/removed
  • m
    Narrator: and this is how he tricks people into finding and fixing bugs and submitting pull requests folks, a real pro
  • w
    Thanks for suggesting this: I ended up finding my problem was that I had another element ~~(not a parent or child of the form) with 
    hx-indicator
    class on it. ~~ actually, it was the 
    body
    tag that had an 
    hx-indicator
    attribute, so I don't think this is really a bug. This caused line 1691 to trigger and set 
    indicators
    to an empty list (via 
    querySelectorAllExt
    ) instead of setting it to an array containing the form instance (line 1693) Do you think this is a bug?
  • m
    it sounds like it, can you log a bug about it and then fix it 😉
  • w
    I edited my comment above, I was a bit mistaken. I think it was more a user error than a bug, since there was a parent tag (
    <body>
    ) that had an 
    hx-indicator
    attribute.
1...546547548...1146Latest