Upcoming WHATNOT meeting on 2024-08-08

[cwilso]

What is the issue with the HTML Standard?

Today we held our weekly triage call (#10534) and I will post the meeting notes there in a bit. The next one is scheduled for August 8, 1am PDT. Note that this is 1 week later in an EU-JP friendly time.

People interested in attending the next call please respond here or reach out privately to @past, @cwilso 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 this meeting. Here are the notes from this meeting (the next one is at #10556):

Agenda

Attendees: Emilio Cobos Álvarez, Olli Pettay, Simon Pieters, Kagami Rosylight, Yoav Weiss, Domenic Denicola
Scribe:

1. Review past action items
   1. None
2. Carryovers from last time
   1. Yoav will ask Artur and Arthur to comment on the Severing a document's opener relationship regardless of origin issue.
      1. Seems like we've got comments from both.
      2. Can take off the agenda until Anne (and Yoav) are back.
   2. Validating internationalized mail addresses in <input type="email">
      1. Still no Anne or Henri, carry over until they show up.
   3. [rendering] animation frame callback handling when iframes are involved
      1. Seems like it's making progress, probably can take it off the agenda.
      2. People on the call suggest looking at the blame to answer the latest questions about unnecessary rendering.
3. New topics
   1. Stylable <select> element · Issue #9799 · whatwg/html · GitHub
      1. Pull request: Define customizable <select> #10548
      2. Joey is looking for stage 2: https://whatwg.org/stages#stage2
      3. Olli really doesn't like it being MutationObserver timing for the scheduling. Unclear whether that should block stage 2.
      4. Probably should carry over
   2. Proposal: CSS reading-flow
      1. Maybe this was covered last week and the agenda+ label was not removed? Based on Proposal: CSS reading-flow #10407 (comment)
      2. Olli: are there any shadow DOM specific concerns?
      3. Emilio: it could interact, e.g. flexbox + slots would change the tabbing order.
      4. Domenic: since there's already a shadow DOM + focus tabbing spec, they'll be modifying that, and thus they'll have to figure out the right order.
      5. Simon: CSS reading-order will also affect the accessibility tree, but that isn't defined anywhere… It would be good to define it.
   3. Errors when attaching a declarative shadow root · Issue #10527 · whatwg/html · GitHub
      1. Simon: my initial reaction is to only do console errors. Nonzero XSS risk from the parser being able to trigger the error event.
      2. Nobody else had many thoughts, so we'll probably go with that.
   4. Discussing how to focus navigate display: contents elements that are focusable in CSS reading-flow · Issue #10533 · whatwg/html · GitHub
      1. Maybe this was covered last week and the agenda+ label was not removed? Based on Discussing how to focus navigate display: contents elements that are focusable in CSS reading-flow #10533 (comment)
   5. [Because we had extra time] FYI Multiple import maps #10528 exists
      1. Olli: existing processing model has been weird in terms of combination with speculative loading.
      2. Yoav: can you give more details?
      3. Olli: can't fully remember…

Action Items

1. Mozilla folks to decide whether they're happy with stage 2 for <select>. (And Apple folks should as well, but they weren't on the call.)
2. @smaug---- to report back with more detail on what he found weird in the import maps processing model.

Minutes

Forgot to scribe…