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 6/15/2023 #9375

Closed
past opened this issue Jun 2, 2023 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 6/15/2023 #9375

past opened this issue Jun 2, 2023 · 1 comment
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Jun 2, 2023

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

@past
Copy link
Author

past commented Jun 15, 2023

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

Agenda

Attendees: Joey Arhar, Panos Astithas, Mason Freed, Brian Kardell, Anne van Kesteren, Olli Pettay, Simon Pieters

  1. Review past action items
    1. Domenic to write up a response for Accessibility Attribute Request focused on: is there implementer interest? And the general question of dashes in attribute names.
      1. Done.
    2. Google folks to collect some statistics on how often various queue lengths are overflowed around the BroadcastChannel + bfcache proposal. Anne will check if we can move forward with evicting on implementation-defined queue limit exceeded, with 2/3 support and 1 not-persuaded but not strongly objecting.
      1. Done.
  2. Carryovers from last time
    1. [Brian] Update the :dir / directionality to include shadow dom (was Tests for directionality and shadow DOM)
      1. Olli will take a look at the latest changes. Mason and Joey will take another review pass.
    2. [Anne] Reference even more baseline concepts in CSS Inline Layout
      1. Mason will find someone from Chrome to review.
  3. New topics
    1. [Panos] It would be great if people could RSVP to the calendar invite before the meeting so we know who to wait for.
    2. [Mason] Can we prioritize/list the important open issues for Popover?
      1. Mason will add the "addition/proposal" label to the non-blocking ones.
      2. Anne appreciates anyone who helps triage such issues by adding "addition/proposal" when appropriate.
    3. [Panos] Meeting at TPAC.
      1. Panos to ask the CSS and a11y folks if they want to meet jointly and file an issue with a proposed agenda.

Action Items

  1. @smaug---- will take a look at the latest changes in Update the :dir / directionality to include shadow dom. @mfreed7 and @josepharhar will take another review pass.
  2. @mfreed7 will find someone from Chrome to review Reference even more baseline concepts in CSS Inline Layout.
  3. @mfreed7 will add the "addition/proposal" label to the non-blocking issues for Popover.
  4. @past to ask the CSS and a11y folks if they want to meet jointly at TPAC and file an issue with a proposed agenda.

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

1 participant