Upcoming WHATNOT meeting on 11/30/2023

[past]

What is the issue with the HTML Standard?

Today we held our biweekly triage call (#9909) and I will post the meeting notes there in a bit. The next one is scheduled for November 30, 9am PDT. Note that this is 2 weeks later in an America+Europe friendly time.

People interested in attending the next call please respond here or reach out privately to me or the spec editors. We will be tagging issues for the next call again using the agenda+ label in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.

[past]

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

Agenda

Attendees:Panos Astithas, David Baron, Mason Freed, Anne van Kesteren , Keith Cirkel, Emilio Cobos Álvarez, Noam Rosenthal, Olli Pettay, Joey Arhar, Sanket Joshi, Chris Wilson, Sanket Joshi, Vladimir Levin

1. Review past action items
   1. Noam to create an issue on GitHub to track speccing and web-exposing restoration of tabs.
      1. Done
   2. Noam will investigate this microtasks + event handlers issue, and report back.
      1. Appears to be a Firefox issue, Noam discussed it with Olli. Not a spec issue.
   3. Simon to look more into nested interactive content spec behavior, with synthetic click events.
      1. Carryover
   4. Anne to get James Craig involved in the nested interactives/summary discussions.
      1. Reached out to James, waiting to hear back.
   5. Domenic & Anne to figure out what we're doing with enumerated attributes and help land Keith's PRs.
      1. PRs landed!
2. Carryovers from last time
   1. Anne to provide feedback on Add steps to destroy documents that are ineligible for receiving message when posting message through broadcast channel.
      1. Done
   2. [Emilio] :active and activating via the keyboard
      1. David: there is even more confusing behavior than what is already mentioned
      2. Olli asks for the interaction with key repetition and mouse down/up
      3. Emilio: feature seems useful in general, how do we spec it in a sensible way?
      4. David will post more context about weird behavior in the issue
      5. David described the difference between space and enter in a nested input field in a summary for Blink.
      6. Emilio suggests tying activation to keyup/keydown
      7. Mason mentioned it was probably better to make the model closer to how mouse works (in terms of active chain and such)
3. New topics
   1. [Mason] Add getInnerHTML() that optionally serializes declarative Shadow DOM
      1. Mason: there seems to be agreement on the usefulness, but not on the shape of the API. Describes the few options available.
      2. Olli suggests we need to be consistent with getComposedRanges
      3. Mason and Anne discuss the server-side SSR use case
      4. Anne suggests to use the same code for open and close shadow roots
      5. Keith suggests adding a lifecycle hook to participate in the API
      6. Anne and Mason agree on an API shape that includes a list of nodes and a boolean
      7. Mason will summarize in the issue.
   2. [Olli] autocomplete tokens for EID and IMEI
      1. Olli fears that this may be a slippery slope towards adding things that are not applicable to general web browsers
      2. Noam suggests using a registry like we do elsewhere in the platform
      3. WebKit and Blink are OK with this, Gecko is opposed.
      4. Anne will add a comment explaining the ways a general purpose browser and website can use this to help some set of users
   3. [Noam] [View Transition] Event on old Document to set transition state
      1. The discussion helped Olli understand what the requirements are, so more discussion will continue in the issue.

Action Items

1. @dbaron will post more context about weird behavior in the :active and activating via the keyboard issue
2. @mfreed7 will summarize the consensus in the Add getInnerHTML() that optionally serializes declarative Shadow DOM issue
3. @annevk will add a comment to autocomplete tokens for EID and IMEI explaining the ways a general purpose browser and website can use this feature to help some set of users