Vincent
Vincent
The suggested changes should fix the following issues: - #1506 => values of clicked submit buttons defining a name/value pair, are now correctly included in the request payload - #1120...
Adds support for comma separated list of event names to the `HX-Trigger` response header. Currently, to trigger multiple events with that header, you have to use the JSON syntax, even...
It's a pretty common pattern to define trigger events using the `from:body` syntax. The issue: this "body" selector currently results in a call to `document.querySelectorAll` inside [`querySelectorAllExt`](https://github.com/bigskysoftware/htmx/blob/master/src/htmx.js#L591) While this may...
When specifying a `hx-trigger` attribute, `getTriggerSpecs` tokenizes & parses the trigger spec string everytime it's called. This isn't an issue for most cases, but it performs poorly when operating on...
This addresses issue #1509 - `hx-include` supports the extended selectors, which were not mentioned in its documentation - The behaviour of `find` for example, can be confusing when using an...
I'm very often using the following pattern : ```html ``` clicking on the button brings in a popup, in place of a initially empty element. The relative parent allows positioning...
This fixes #1496 Typing `formElement.anything` returns all inputs declaring that `anything` as their name, as an object or an array if there are several of them. You can observe this...
As discussed in the Discord with @1cg : The current state for HTML elements with hx-attributes is conform to the behaviour of a HTML form, where having file inputs do...
Using `changed` along `from` in [`hx-trigger`](https://htmx.org/attributes/hx-trigger/) seems to have an unexpected behaviour. Given the following code (you can also play it in [this JSFiddle](https://jsfiddle.net/7ygfa9zn/)): ```html Search Category A B C...