Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upcoming HTML standard issue triage meeting on 11/2/2023 #9874

Closed
past opened this issue Oct 20, 2023 · 4 comments
Closed

Upcoming HTML standard issue triage meeting on 11/2/2023 #9874

past opened this issue Oct 20, 2023 · 4 comments
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Oct 20, 2023

What is the issue with the HTML Standard?

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

@past past added the agenda+ To be discussed at a triage meeting label Oct 20, 2023
@Pandapip1
Copy link

I would be interested in attending. #9865

@fergald
Copy link

fergald commented Oct 31, 2023

I would like to attend for:

@past
Copy link
Author

past commented Oct 31, 2023

I added you both and tagged the topics with agenda+ (except for the webappsec one, I'll add that to the meeting notes separately).

@past
Copy link
Author

past commented Nov 2, 2023

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

Agenda

Attendees: Michael Smith, Joey Arhar, Panos Astithas, Fergal Daly, Sanket Joshi, Olli Pettay

  1. Review past action items
    1. Panos will tag Simon and Alastor on Add TextTrackCue ctor & cue + cuebackground attributes.
      1. Done.
    2. Domenic and Hiroshige to comment on Use inside settings to fetch the descendants of module worker in the worker module script graph.
      1. Hiroshige needs more time to discuss this with his team.
    3. Domenic and Hiroshige to comment on Should throw SecurityError when loading a worker with a cross-origin script.
      1. Done.
    4. Olli will review Fix errors related to elements in auto directionality traversal.
      1. Done.
  2. Carryovers from last time
    1. None.
  3. New topics
    1. [Fergal] Add steps to destroy documents that are ineligible for receiving message when posting message through broadcast channel
      1. Chrome and Firefox agree that we should spec something here, perhaps starting with a conservative approach. We need Anne to provide feedback from WebKit.
    2. [Gavin] subcaption / nested caption tag
      1. Will discuss when the proposer is available to present the topic.
    3. [Fergal] Add back/forward cache NotRestoredReasons
      1. Agreement to proceed with the conservative approach for now. Agreement to use an object to display a message in devtools. Yuzu will update the PR.
    4. [Fergal] Add section for BFCache eviction in cache clearing
      1. Olli is supportive and will discuss it internally next week. Will comment on the issue afterwards.
    5. [Joey] Event bubbling and which events are blocked in disabled form controls
      1. Agreement that double-click should be blocked when click is blocked.

Action Items

  1. @annevk to provide feedback on Add steps to destroy documents that are ineligible for receiving message when posting message through broadcast channel.
  2. @rubberyuzu to update Add back/forward cache NotRestoredReasons.
  3. @smaug---- to comment on Add section for BFCache eviction in cache clearing.

@past past closed this as completed Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ To be discussed at a triage meeting
Development

No branches or pull requests

3 participants