Vincent

Yeah we had to run a trick for this to keep the core extensions' documentation be on the main website, if you look at this repo's [`sse` folder](https://github.com/bigskysoftware/htmx-extensions/tree/main/src/sse), you'll see...

Hey, as it's a niche usecase, I would recommend either: - Adding a [`htmx:configRequest` event](https://htmx.org/events/#htmx:configRequest) listener in your JS to modify the request's URL through `event.detail.path` (just realized that this...

Personal opinion: `hx-on` is fine for simple usecases where you have a simple call, like a `form.reset` after a request or stuff like that. I feel like as soon as...

Thanks!

After discussion with @1cg, here's the direction this PR should take: - add a syntax support for enclosing comma-selectors with extended ones, in the format `closest ` (cf `normalizeSelector`) -...

Damn, that's an interesting benchmark, thanks for looking into it @MichaelWest22 ! I wouldn't have expected to be such a difference compared to using substring Just added an extra length...

Sure, done @1cg Pushed a `npm run format` fix along, as otherwise the CI fails on the linting step

Hey, the way that `hx-trigger` works is that, when initializing the node that declares this attribute, htmx will bind listeners to all elements matching that selector. So when your `hx-trigger="click...

I'm not gonna lie ; I always use hx-trigger's `from` keyword with `from:body`, mostly for headers sent from the server (to trigger some refreshes along a response), or for say...

Note that you can also use the `from` modifier of [hx-trigger](https://htmx.org/attributes/hx-trigger/) For example, defining ```html ... ``` will catch the `change` event on the form itself (thus on any contained...