Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion for Proposal: asynchronous event listeners #101

Open
mmocny opened this issue Sep 21, 2024 · 4 comments
Open

Discussion for Proposal: asynchronous event listeners #101

mmocny opened this issue Sep 21, 2024 · 4 comments
Labels
session Breakout session proposal

Comments

@mmocny
Copy link

mmocny commented Sep 21, 2024

Session description

There is a proposal for async event listeners: whatwg/dom#1308

Several use cases identified as related (whatwg/dom#1308 (comment)):

  • "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)

#async-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

Links to calendar

Meeting materials

@mmocny mmocny added the session Breakout session proposal label Sep 21, 2024
@tpac-breakout-bot
Copy link
Collaborator

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
Copy link
Member

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.

@tidoust
Copy link
Member

tidoust commented Sep 22, 2024

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.

Just to confirm that the session was added to the schedule (at 16:00), see https://www.w3.org/events/meetings/df616a60-8591-4f24-b305-aa0870aac1cb/

@mmocny
Copy link
Author

mmocny commented Sep 23, 2024

Thank you for accommodating this session, even when it was submitted past deadline! (Apologies for that)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal
4 participants