Upcoming HTML standard issue triage meeting on 6/1/2023

[past]

We skipped the last biweekly triage call (#9254), which means there will be more things to discuss in the next one, scheduled for June 1, 1 am PDT. Note that this is 2 weeks later in a Europe+APAC 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 yesterday! Here are the notes from this meeting (the next one is at #9375):

Agenda

Attendees: Domenic Denicola, Olli Pettay, Kagami Rosylight, Peter Van der Beken, Anne van Kesteren

1. Review past action items
   1. Anne will get WebKit feedback, Emilio tagged Mozilla folks for feedback on Standardize rendering of PQ and HLG HDR image content.
      1. Anne: ongoing.
   2. Anne and Olli will provide feedback for Detect UA transitions on same-document navigations or find others to do so.
      1. Still ongoing.
   3. Shu will send an HTML PR after the clarifications that were discussed around Atomics.waitAsync integration.
      1. Done.
2. Carryovers from last time
   1. Emilio will help advise how to make the CloseWatcher spec more rigorous, and Domenic will work on upstreaming it to HTML.
      1. Still in the list of things to get to.
   2. [Anne] Accessibility Attribute Request
      1. Domenic to write up a response focused on: is there implementer interest? And the general question of dashes in attribute names.
   3. [Anne] HTML cross-document encoding inheritance with bogus Content-Type charset
      1. Some sentiment that this is such an edge case, aligning on the 2/3 behavior should be fine. But, postponed until Henri can give an opinion from Gecko's side.
   4. [Fergal] BroadcastChannel + bfcache proposal
      1. Anne responded with WebKit's perspective.
      2. Google folks to collect some statistics on how often various queue lengths are overflowed.
      3. Some discussion of whether this should be consistent with storage events. Maybe not since storage events don't carry info.
         1. Session storage and changing browsing contexts storage#119 (comment)
      4. Anne/WebKit would be open to queueing with implementation-defined behavior when the queue limit is exceeded. Others on the call are not too happy with that...
      5. Anne would like to see a real-world site that would work with replayed messages
      6. Anne will check if we can move forward with evicting on implementation-defined queue limit exceeded, with 2/3 support and 1 not-persuaded but not strongly objecting.
         1. Numbers would help.
   5. [Brian] Update the :dir / directionality to include shadow dom (was Tests for directionality and shadow DOM)
      1. Didn't discuss this.
3. New topics
   1. [Anne] Reference even more baseline concepts in CSS Inline Layout
      1. Didn't discuss this.

Action Items

1. @domenic to write up a response for Accessibility Attribute Request focused on: is there implementer interest? And the general question of dashes in attribute names.
2. Google folks to collect some statistics on how often various queue lengths are overflowed around the BroadcastChannel + bfcache proposal. @annevk will check if we can move forward with evicting on implementation-defined queue limit exceeded, with 2/3 support and 1 not-persuaded but not strongly objecting.