Upcoming HTML standard issue triage meeting on 10/5/2023

[past]

Today we held our biweekly triage call (#9629) and I will post the meeting notes there in a bit. The next one is scheduled for October 5, 1am PDT. Note that this is 4 weeks later in a Europe+APAC friendly time. We will be skipping the scheduled meeting at 9/21 since we will be meeting again next week (9/14-915) at TPAC.

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.

[annevk]

We have had some issues with people not being able to join because nobody present could approve them. And not everyone has a Google account we would be able to add to the invite. It would be great if we could find some kind of solution for that for next time.

[annevk]

Attendees: smaug, kagami, annevk, zcorpan, marcos, mike[tm], keith

Review past action items

• Olli will add a comment before TPAC to [View Transitions] Extend render-blocking to support Document, where we will discuss this further.
  • This was discussed at TPAC.
  • Olli will add a comment asking for a summary of the TPAC discussion.

Carryovers from last time

• [Anne] Use inside settings to fetch the descendants of module worker in the worker module script graph
  • Discussed at TPAC.
  • Needs to continue to be carryover due to lack of Google presence.

New topics

• [Keith] Add autopause attribute to media elements to allow automatic pausing of media
  • Simon will add comments to this issue and the linked issue.
• [Anne] Should throw SecurityError when loading a worker with a cross-origin script
  • Needs to be carryover due to lack of Google presence.
• [Marcos] Add TextTrackCue ctor & cue + cuebackground attributes
  • Simon will take a look.

[past]

We have had some issues with people not being able to join because nobody present could approve them. And not everyone has a Google account we would be able to add to the invite. It would be great if we could find some kind of solution for that for next time.

Sorry about that, and thanks for persevering despite the difficulties. I guess this is the first time nobody from Google could join.

I don't think a Google account is necessary and we have already invited several people with their non-Google email addresses. But I went ahead and added some folks as co-hosts (including the editors) to avoid approval issues in the future. I plan to cancel meetings when none of these folks can attend or add more co-hosts as necessary.