Re: [whatwg/dom] Proposal: asynchronous event listeners (Issue #1308)

> - "async effects which follow the sync event"
>
>    - Might still want to be able to preventDefault etc from the async., e.g. form validation which needs a network hop first.

Being able to arbitrarily delay (and as a result re-order) default actions could have pretty far reaching complexity and implications.

I suspect for security reasons we might need to have a limit on how long a default action could be delayed and still executed, this reminds me a bit some of the async user activation use cases and could be a better way to handle it (having a direct link from the event to the user-activation requiring API), though we likely still need to support the model we have today. @mustaqahmed

I think we'd have to look through the different default actions and figure out whether they make sense to be possible to be delayed. E.g. we probably don't want to delay the default action of `touchdown` starting a scroll, and preventing the touch from turning into compatibility gestures like click.

Similarly there may be groups of default actions which don't make sense to be re-ordered. E.g. delaying setting focus while still clicking on the element?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1308#issuecomment-2361298219
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1308/2361298219@github.com>