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

[past]

What is the issue with the HTML Standard?

Today we held our biweekly triage call (#9706) and Anne has already posted the meeting notes there. The next one is scheduled for October 19, 9am PDT. Note that this is 2 weeks later in a Europe+America 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.

[RitamDas30]

Interested

[annevk]

Hey @RitamDas30 if you could state what you'd be interested in discussing that would help. Also, we'll need your email address to be able to invite you.

[RitamDas30]

I am a newbie in open source community/ open source projects, I am looking for how I can contribute to this project. Here is my email for future communication: ritamdas238@gmail.com

[annevk]

@RitamDas30 I invited you to the November 3 meeting. You should have an email (search for WHATNOT). I forgot to add you in time for yesterday's meeting but it wasn't very eventful anyway.

[past]

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

Agenda

Attendees: Panos Astithas, David Baron, Keith Cirkel, Emilio Cobos Álvarez, Vladimir Levin, Olli Pettay, Noam Rosenthal, Kagami Rosylight, Anne van Kesteren

1. Review past action items
   1. Olli will add a comment to [View Transitions] Extend render-blocking to support Document asking for a summary of the TPAC discussion.
      1. Done.
   2. Simon will add comments to the Add autopause attribute to media elements to allow automatic pausing of media issue and the linked issue.
      1. Done.
   3. Simon will take a look at Add TextTrackCue ctor & cue + cuebackground attributes
      1. [emilio] Alastor commented on the Mozilla standards-positions. Maybe tag them both explicitly?
2. Carryovers from last time
   1. [Anne] Use inside settings to fetch the descendants of module worker in the worker module script graph
      1. Will ask Domenic and Hiroshige to comment.
   2. [Anne] Should throw SecurityError when loading a worker with a cross-origin script
      1. Will ask Domenic and Hiroshige to comment.
3. New topics
   1. Noam would love to finish the deferred fetching issue. Anne and Olli think the names are fine. Noam will look into cross-document permissions. BackgroundSync was discussed as a potential thing to imitate, but agreed that it's unlikely the right one since there is no consensus about it among browser vendors.
   2. David wants Olli's review on Fix errors related to elements in auto directionality traversal.

Action Items

1. @past will tag @zcorpan and @alastor0325 on Add TextTrackCue ctor & cue + cuebackground attributes.
2. @domenic and @hiroshige-g will comment on Use inside settings to fetch the descendants of module worker in the worker module script graph.
3. @domenic and @hiroshige-g will comment on Should throw SecurityError when loading a worker with a cross-origin script.
4. @smaug---- will review Fix errors related to elements in auto directionality traversal.

[domenic]

2. @domenic and @hiroshige-g will comment on Use inside settings to fetch the descendants of module worker in the worker module script graph.

I think Chromium has already commented on this issue.

3. @domenic and @hiroshige-g will comment on Should throw SecurityError when loading a worker with a cross-origin script.

I will ping again for a reply.

[annevk]

Chromium did comment on the first issue, but there was some pushback you didn't engage on.