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

[past]

Today we held our biweekly triage call (#9002) and I will post the meeting notes there in a bit. The next one is scheduled for April 6, 4 pm PDT. Note that this is 2 weeks later in an America+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 today! Here are the notes from this meeting (the next one is at #9132):

Agenda

Attendees: @past, @cwilso, @domenic, @josepharhar, @smaug----

1. Review past action items
   1. Someone from WebKit should comment on Tests for directionality and shadow DOM.
      1. Still outstanding.
2. Carryovers from last time
   1. [Domenic] Sandboxed iframes without allow-same-origin and with about:blank or about:srcdoc urls should not inherit a fallback base url
      1. Chrome will continue to explore the best web-compatible solution and come up with a proposal.
3. New topics
   1. [Domenic] Modernized version of window.open() API
      1. Domenic to look into anchor element interactions. Olli to look more into the issue and comment.
   2. [Hsinyi] Clarify the sequential focusing behaviour when the current focused element is not in the sequential navigation order
      1. Joey will explain why Chrome behaves this way. Domenic will clarify his reading of the spec.
   3. [Anne] Accessibility Attribute Request
      1. Will revisit this when Anne is present.
   4. Domenic notes that there are a lot of popover issues in progress, offered to help if people need any help.

Action Items

1. Someone from WebKit should comment on Tests for directionality and shadow DOM.
2. @domenic to look into anchor element interactions for Modernized version of window.open() API. @smaug---- to look more into the issue and comment.
3. For Clarify the sequential focusing behaviour when the current focused element is not in the sequential navigation order @josepharhar will explain why Chrome behaves this way. @domenic will clarify his reading of the spec.