- From: Andrea Giammarchi <notifications@github.com>
- Date: Thu, 19 Sep 2024 08:23:08 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 19 September 2024 15:23:12 UTC
@flackr links to delayed activations is in my previous comment: https://github.com/whatwg/dom/issues/1308#issuecomment-2313072164 I agree some event doesn't want that activation but your *gesture* example is spot-on: the whole clicking is a delayed event, why can't that event await before landing the user into a different page or avoid submitting that form already? So :+1: to me about defining non-async-friendly events (I think these are an easy/small list related to mouse or touch movements or scrolling and not much else) and those that could wait a *transient* time before firing out of the blue. The fact *transient events* exist in the first place should be a strong indication the synchronous API defined "ages ago" when no `async` existed in the first place might need some modernization for current APIs which are 99% of the time asynchronous anyway. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1308#issuecomment-2361330274 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1308/2361330274@github.com>
Received on Thursday, 19 September 2024 15:23:12 UTC