* Update hx-trigger.md
- Added a clarification in notes to suggest adding a delay when adding reset to hx-trigger.
- Also thought it's useful to add a reference to MDN's list of web API events, as it was one of the omissions in the hx-trigger doc which made me Google a little when I started out.
* Update hx-trigger.md
My bad, you're absolutely right. I've rewritten the proposed changes with your explanation in mind.
* Clarify event filter uses in hx-trigger
* Change hx-trigger event filter example to avoid ambiguity
input is both a tag and an event.
* Document the scope difference between standard selector and event filter
from:input listens to the page and click[event.target.matches('input')] listens to the element.
* Document that event filters as an alternative to CSS selectors require eval
* Move note about eval to standard event filters section.
* Simplify the referenced to standard event filters in the standard event modifiers section, and link to the standard event filters section instead.
* End quote in the correct place in standard event modifier doc.
* Correct language on how event filters from:body receive events.
* hx-trigger filter example catches click events specifically.
* Add more information about other swap strategies
* Change suggested by @MichaelWest22
* Grammar error as per comments from @Telroshan
* Clarification requested by @Telroshan
This update clarifies the hx-disabled-elt attribute's ability to accept multiple CSS selectors, separated by commas, enabling developers to disable multiple elements simultaneously during an HTTP request.
* Add config option to ignore nested oob swaps
* Fix oobElement root check
* Save config between tests; repeat some tests with different configs
* Add tests for oob-swaps in html, body tags
* Don't unnecessarily change const to var
This note would have really helped me when I was working on avoiding my
maplibre canvas div from being overwritten when using hx-boost. I was
initially confused by the hx-boost=false not thinking that is what I
needed.
* Allow CSS selectors with whitespace in `hx-trigger`
Parsing of `hx-trigger` scans for whitespace, so if a CSS selector is used that contains whitespace, e.g. `form input`, a syntax error is raised.
A workaround is implemented by allowing such a CSS selector to be wrapped in either curly braces or parentheses.
* Add explanation whitespace in CSS selector to docs
* Tests for CSS selectors containing whitespace
* Use faster RegEx test, remove redundant variable declarations
* Added Descendant Combinator support to `root` and `target` modifiers
* Add missing semicolon
* Tests for descendant combinators in `root` and `target` modifiers
* Improve descendant combinator test coverage
