Discussion for Proposal: asynchronous event listeners

[mmocny]

Session description

There is a proposal for async event listeners: https://github.com/whatwg/dom/issues/1308

Several use cases identified as related (https://github.com/whatwg/dom/issues/1308#issuecomment-2312993127):

• "passive" event dispatch. Observe, but don't block, event dispatch. Don't need preventDefault.
• lazy loading "controllers", aka progressive hydration.
• Tracking long running "async effects" which follow the sync event dispatch.
• "document still loading" use cases
• "document started unloading" use cases

Session goal

Discussion and sharing early feedback.

Additional session chairs (Optional)

@domfarolino

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

discussion-for-proposal-asynchronous-event-listeners

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

No response

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

[domfarolino]

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

I'm not sure how accurate this is. Since we're past the breakout proposal deadline, we might want to reach out to someone directly to make sure this gets scheduled accordingly.