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 8/18/2022 (new time!) #8162

Closed
past opened this issue Aug 5, 2022 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 8/18/2022 (new time!) #8162

past opened this issue Aug 5, 2022 · 1 comment
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Aug 5, 2022

Yesterday we held our monthly triage call (#8089) and I will post the meeting notes there in a bit. The next one is scheduled for August 18, 4 pm PDT, per #8106. Note that this is 2 (not 4) weeks later in an APAC+US friendly (not US+Europe friendly) time, as discussed.

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 and we would like to invite anyone that can contribute to said issues to join us.

@past
Copy link
Author

past commented Aug 19, 2022

Thanks everyone for attending! Between the 2-week cadence and the shortened duration of the meeting (per #8106) we discussed fewer topics than usual. Here are the notes from this meeting (the next one is at #8208):

Agenda

  1. Review past action items
    1. Eric will check with Elika about the tests for the PR for directionality in the shadow DOM.
      1. Olli started reviewing and has left a question in the PR.
    2. Emilio will work on a concrete proposal for Define OffscreenCanvasRenderingContext2D.font setter in detail.
      1. No progress.
    3. Mason will draft a PR for Scoped Custom Element Registries.
      1. Mason is trying to find someone to draft the PR and will bring it up when it's ready.
    4. Domenic will comment on the dialog element individual blockers with his opinion on how blocking/non-blocking they are toward further progress.
      1. Done.
    5. Mason will update the group next time with even more test data from the autocomplete attribute for street-address details issue.
      1. Data gathering is ongoing, and we'll revisit this when it's done.
    6. Panos will update the calendar invite with the new agreed upon times.
      1. Done.
  2. Carryovers from last time
    1. [Emilio] focus delegate code seems wrongly only looking at children
    2. [Emilio] autofocus + delegateFocus handling doesn't make much sense to me
      1. Domenic sent a PR for both. Unclear if there is test coverage for this. Emilio/Domenic/someone should figure it out.
  3. New topics
    1. [Domenic] Clarify UX (keyboard) and further a11y expectations for modeless dialogs
      1. Usage numbers are tempting for deprecation/removal. Will wait to get more experience from the pop-up API before exploring further. Domenic will comment on the thread.

Action Items

  1. Someone else will have to chair the meeting next time. @domenic volunteered.
  2. @meyerweb to respond to @smaug----'s review feedback in the PR for directionality in the shadow DOM.
  3. @emilio/@domenic/someone should figure out if there is test coverage for focus delegate code seems wrongly only looking at children.
  4. @domenic will comment on the Clarify UX (keyboard) and further a11y expectations for modeless dialogs thread.

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