Upcoming WHATNOT meeting on 4/18/2024 about html HOT 4 CLOSED

I18N would like to continue the review we started in March. I will make a prioritized list of issues.

from html.

I'd like to start the discussion about the web integration of the TC39 AsyncContext proposal, for which I opened an issue at tc39/proposal-async-context#82.

from html.

Hi @whatwg/triage! There are no agenda topics for this instance, so please tag any that need to be discussed. I am not canceling this as I will not be attending and there may be last-minute additions that I won't see on time, but feel free to skip if there are no topics and/or low attendance.

from html.

Thank you all for attending the meeting today! Here are the notes from this meeting (the next one is at #10287):

Agenda

Attendees: Michael Smith, Andreu Botella, Domenic Denicola, Keith Cirkel, Kagami Rosylight

1. Review past action items
   1. Mason will ping Domenic about Focus delegate algorithm doesn't consider elements assigned to slot.
      1. Done.
   2. Mason or Joey will add comments with the different developer ergonomics of the various options for Add anchor attribute.
      1. Done.
   3. Olli wants to think through the removal case for Gecko and test other browsers for Introduce DOM post-insertion steps. Noam will share with Olli a document with the results of Dominic's and Noam's investigation into Blink.
      1. [smaug] reviewed the PR again, and it doesn't seem to handle mutations and not even match what Blink does
2. Carryovers from last time
   1. None.
3. New topics
   1. [Addison] Joint session with the I18N WG. Addison will provide a list of topics.
      1. Addison was unavailable.
   2. [Andreu] Integrating AsyncContext to web APIs
      1. Thoughts from Domenic:
         1. Complex! Hard to give specific advice.
         2. Probably don't do cross-document navigations, unless there are strong use cases. Data point: navigation API promises don't resolve for cross-document.
         3. I like the division into categories. That will also be helpful for writing a guide going forward for future APIs.
         4. Adding complexity to specs is manageable, but adding complexity to user-facing API with an event listener option requires a bigger explainer-like thing about what use cases are impossible without it, how it will be used, etc.
            1. Andreu: main use case is tracing-style libraries that will probably monkeypatch addEventListener() and change the option value depending on the event type.
      2. Keith:
         1. Olli from Mozilla might have concerns about event dispatch being a hot path.
         2. Be sure to investigate observables, maybe coordinate with Dom Farolino

Action Items

1. None.

from html.