looked up hx-trigger in the reference the 3rd bullet point here https://htmx.org/attributes/hx-trigger/

it was the reference, not the docs page

Ah, totally missed that. Thanks!

Just tested, but does not seem to work. When I use this:

hx-trigger="itemAdded, itemDeleted from:body"

Then only

itemDeleted

works. When I do this:

hx-trigger="itemAdded , itemDeleted from:body"

Then only

itemAdded

works.

I think you need to repeat

from:body

Indeed! Thanks for the tip! So this works:

hx-trigger="itemAdded from:body, itemDeleted from:body">

Ok 🙂 opened an issue for it https://github.com/bigskysoftware/htmx/issues/585

A week ago, i had a use case which is a bit complicated (Link: https://discord.com/channels/725789699527933952/725789747212976259/882353638394167386), and now i'm struggling to make a working example to share, because much of the content is loaded in dynamically via hx-get and if i put that all on one page, the example would be trivial. Any ideas how to discuss such things? For my discussion point, I'm just not able to communicate it, but it works as it stands now, so I'm not worried too much. Just to tell that i did not forget that.

Will htmx work on schedule paths or groups?

Will htmx work on svg paths or groups?

I’m not at my computer so I can’t try it. Just curious

I know someone was playing around with svgs previously, we should create an example if it works

yeah, looks like you need to use the morphdom extension to get it to work: https://discord.com/channels/725789699527933952/725789747212976259/869415720776269904

No wories, I have noticed this as well that w/ htmx it can be hard to put together examples, since you need a server side

@User 👀 https://github.com/bigskysoftware/htmx/commit/a1d320243d1a3d3e7c7235c7e6ab28425e9a3bfe

ey channel whats wrong with these: https://github.com/zodman/htmx/blob/master/test/ext/path-deps.js#L173

Maybe just debug it? It's not much code

@mysterious-toddler-20573 i see the https://github.com/zodman/htmx/blob/master/src/ext/path-deps.js#L29 is htmx.trigger

but the hx-get never happend

Ah, that's an artifact of the test framework we are using. There are two requests, so you have to call

server.respond()

twice:

js
    it("path-deps regression test", function () {
        this.server.respondWith("POST", "/entries/12", "Deps fired!");
        this.server.respondWith("GET", "/message/", "<li>message showed</li>");
        var div1 = make('<div hx-ext="path-deps">' +
            '<ul id="ul1" hx-get="/message/" hx-trigger="path-deps" path-deps="/entries/*"></ul>' +
            '<button id="buttonSubmit" hx-post="/entries/12">Click Me!</button>' +
            '</div>')
        byId("buttonSubmit").click();
        this.server.respond();
        this.server.respond();
        byId("ul1").innerHTML.should.contains('message showed');
    });

🙂

oh, i just discovered that by looking at the docs. Would this be a good way to say update the number of items in a shopping cart if an item was added? I previously planned to use oob swaps for that, but this seems a bit cleaner.

hx-get works on svg groups and paths so you can make some cool menus

wow, please contribute an example if you have time!

Or just post some basic code and I'll do it

If the path dependencies idea speaks to you, it's pretty clean

it was the way that intercoolerjs worked, but I pulled it out because it confused too many people and so I didn't feel it was a good default

there is a little "spooky action at a distance" but it's according to tastes