Replies: 1 comment 3 replies
-
Hey, I'd say you're completely right, the
Disclaimer: I didn't participate on the hypermedia systems book, but it's likely that those were simply written out of habit, where the authors were not used to the As the book is available on this repository, I can't speak for its maintainers of course, but I'd say feel free to open an issue/PR out there and see how it goes! Hope this helps |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've noticed that both in the Hypermedia Systems book and in may of the examples in the wild, the
hx-trigger
attribute on an input element often uses thechange
event, not theinput
event. I understand the mechanical difference between the two types of events (one fires on any value change while the other fires only when the field loses focus). But, it seems that people use thechange
event in conjunction with thekeyup
event, which feels like it can just be replaced with theinput
event.For example, in the book:
https://hypermedia.systems/htmx-patterns/#_ignoring_non_mutating_keys
... he uses
change, keyup delay:200ms changed
. Why not just useinput delay:200ms
. I feel like this would accomplish the same thing; so, I'm wondering if there's something I'm just missing.If it were just this one time, I'd attribute it to a teaching moment (meaning, he's using this to help showcase the "changed" modifier). But, I see this same pattern a lot in the wild; so I think it must be something I'm just not understanding.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions