Upcoming HTML standard issue triage meeting on 4/20/2023

[past]

Today we held our biweekly triage call (#9070) and I will post the meeting notes there in a bit. The next one is scheduled for April 20, 1 am PDT. Note that this is 2 weeks later in an APAC+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.

[keithamus]

I’m interested

[past]

Happy to add you Keith, I will need your email address to do that. Either email me (pastith at GMail) or let another participant know, if you have interacted with them before.

[past]

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

Agenda

Attendees: @emilio, @fergald, @domenic, @smaug----, @zcorpan, @petervanderbeken

1. Review past action items
   1. Someone from WebKit should comment on Tests for directionality and shadow DOM.
      1. Still no review from WebKit, but it looks like Brian Kardell is working on this with Fantasai.
   2. Domenic to look into anchor element interactions for Modernized version of window.open() API. Olli to look more into the issue and comment.
      1. Carry over Domenic's action item
      2. There's a comment about returning a promise, people should think about that; it's an interesting idea!
         1. Olli says: "would be great", but the big question is when to resolve the promise. Do you get access to the initial about:blank?
         2. What's the earliest point at which resolving would be useful?
   3. For Clarify the sequential focusing behaviour when the current focused element is not in the sequential navigation order Joey will explain why Chrome behaves this way. Domenic will clarify his reading of the spec.
      1. Done and done.
2. Carryovers from last time
   1. [Anne] Accessibility Attribute Request
      1. Anne not present; carrying over
   2. [Domenic] Resetting forms on document reactivation
      1. It turns out this was discussed on a previous call. In general, there are no obvious solutions here, and tradeoffs everywhere. We can remove this from the agenda but welcome anyone who wants to push for a concrete proposal.
3. New topics
   1. [Emilio] popover light dismiss behavior is not specified for Esc key
      1. Discussion of Domenic's CloseWatcher proposal as a solution.
      2. Emilio would prefer to specify keydown instead of leaving it up to the UA.
      3. Emilio will help advise how to make the CloseWatcher spec more rigorous, and Domenic will work on upstreaming it to HTML.
   2. [Anne] HTML cross-document encoding inheritance with bogus Content-Type charset
      1. Carry over, none of the relevant people are on the call.
   3. [Fergal] BroadcastChannel + bfcache proposal
      1. Gecko and Chromium are on board but there's no WebKit person on the call... We can try carrying over.

Action Items

1. @domenic to look into anchor element interactions for Modernized version of window.open() API
2. @emilio will help advise how to make the CloseWatcher spec more rigorous, and @domenic will work on upstreaming it to HTML.