late-king-98305
10/04/2022, 12:15 AMgreen-activity-6102
10/04/2022, 1:53 AMhtmx:responseError
in the events list, this looks like the perfect solutionred-farmer-97020
10/04/2022, 2:05 AMred-farmer-97020
10/04/2022, 2:05 AMred-farmer-97020
10/04/2022, 2:06 AMmost-flag-2080
10/04/2022, 5:45 AMmost-flag-2080
10/04/2022, 5:45 AMrefined-waiter-90422
10/04/2022, 5:58 AMechoing-dress-67727
10/04/2022, 1:10 PMproud-librarian-99598
10/04/2022, 2:00 PMsquare-analyst-94375
10/04/2022, 4:06 PMremove me
call) then I've noticed that HX-Trigger
response headers are aren't triggering my hx-trigger that is watching for the event: (hx-trigger="requestDeleted from:body"
). I'm guessing that the event IS triggered on the element, but it is no longer in the DOM so it doesn't bubble up to the body.
Is there a preferred work around or is this an HTMX bug? Maybe some way to wait for the http request returns before removing the modal?square-analyst-94375
10/04/2022, 4:55 PMmysterious-toddler-20573
10/04/2022, 6:05 PMmysterious-toddler-20573
10/04/2022, 6:07 PMfreezing-waitress-26396
10/04/2022, 6:42 PMmysterious-toddler-20573
10/04/2022, 7:47 PMmysterious-toddler-20573
10/04/2022, 7:47 PMmysterious-toddler-20573
10/04/2022, 8:05 PMmysterious-toddler-20573
10/04/2022, 8:05 PMgreen-activity-6102
10/05/2022, 1:08 AMhx-indicator
right? like for example if i wanted it only to show up when my response takes β₯500 ms to come backgreen-activity-6102
10/05/2022, 1:09 AMgreen-activity-6102
10/05/2022, 1:10 AMmysterious-toddler-20573
10/05/2022, 1:15 AMgreen-activity-6102
10/05/2022, 1:24 AMdisplay
property is not transitionable.. i cant use opacity because im using a big overlay on my table to block clicks during the requestfreezing-waitress-26396
10/05/2022, 4:41 AManimation-delay
property in CSS to transition from 0 opacity to 1, so whenever it shows up it does so with a 500ms delayfreezing-waitress-26396
10/05/2022, 4:41 AMmost-flag-2080
10/05/2022, 5:49 AMproud-librarian-99598
10/05/2022, 10:12 AMdelay
or throttle
with SSE? So should hx-trigger="sse:somethingChangedEvent throttle:1s"
work to only do the hx-get
on that element maximum 1 time per second?
2) I notice that the htmx:sseMessage
event is only emitted if there is an hx-trigger
on that element with an sse
prefix. What I would like to do is to add an htmx:sseMessage
event listener so I can use event.detail.data
to get the data from the SSE message and manually trigger the hx-get
that is on the element that matches with the value in the data of the SSE message.
Or alternatively, someway to do hx-trigger="sse:somethingChangedEvent[filterEvent()]"
where filterEvent
would get access to the data in the SSE message.mysterious-toddler-20573
10/05/2022, 11:26 AMancient-shoe-86801
10/05/2022, 3:00 PM