Andrea Giammarchi

FYI I've proposed to expose `event.waitUntil` when a listener is asynchronous as there's previous work on that within a Service Worker `fetch` listener ... and that didn't go well. [As...

> (But, I don't quite see how waitUntil should help make the initial event dispatch async...) example code I had in mind: ```js anything.addEventListener('name', (event) => { event.waitUntil(new Promise(async (res,...

@mmocny to clarify, I am :+1: on this proposal ... literally anything that will start tackling how to deal with async events, as every new API is async these days...

I don't know if this is useful extra use case or implementation detail, but: > Perhaps a timeout decides when to dispatch the default action? I have worked with SerialPort...

@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...

It’s not possible to do it all in JS so I’ve no idea what latest comment added to this discussion at all.

I haven't seen updates after late September but there is one option that hasn't been discussed: the usage of `{ async: true }` as third argument field: * it can...

> But again, the specific scope of this proposal here I think is limited to the "passive events" use case. I am not sure when that became the case as...

another reason, it's a *live collection*, not a static one, and for short-living content (as that's what nodes in fragments do) makes (imho) very little sense to have, it would...

FWIWI this looks like a no-go to me ... to start with, we need a vDOM specification/standard to adhere ... secondly, the variety of template literals based solutions would beg...