Triggerspec delay unique
Description
If a node has multiple trigger specifications, they should have independent delays. If a single delayed trigger specification is targets multiple nodes, they should share the delay.
Corresponding issue: #2892
Testing
Both variants are explicitly tested. The non-sharing of multiple trigger specifications failed before.
Checklist
- [X] I have read the contribution guidelines
- [X] I have targeted this PR against the correct branch (
masterfor website changes,devfor source changes) - [ ] This is either a bugfix, a documentation update, or a new feature that has been explicitly approved via an issue
- [X] I ran the test suite locally (
npm run test) and verified that it succeeded
Note: the change is on top of #2891
Hey, you'll want to retarget to dev as per our contribution guidelines
Hey, you'll want to retarget to
devas per our contribution guidelines
It was, stupid GitHub UI always chooses the wrong base here.
Thanks!
Note: I'm labelling this as "under discussion" until https://github.com/bigskysoftware/htmx/pull/2891 is processed, as the latter includes some changes that this PR depends on.
It looks like we merged the dependent PR, so if you want to rebase this, please do and re-open the PR.