Upcoming HTML standard issue triage meeting on 7/7/2022

[past]

Today we held our monthly triage call (#7919) and I will post the meeting notes there in a bit. The next one is scheduled for July 7, 9 am PDT. 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]

Thanks everyone for attending! Here are the notes from this meeting (the next one is at #8089):

Agenda

1. Review past action items
   1. Eric to reply to every unresolved comment on the PR for directionality in the shadow DOM and then Olli will take another look.
      1. Olli left more comments. Waiting for Eric's updates.
   2. Domenic will file an issue about Inert subtree section is missing requirement that it should NOT be exposed to accessibility to link any attributes with a11y guidance to HTML-AAM.
      1. Done.
   3. Domenic and Anne to merge the Canvas2D Filters revert to the spec, Domenic to send a PR to move the tests.
      1. Tests moved, spec PR will be merged soon.
   4. Mason will take a look at Remove UA style for h1-h6 in section (et. al.) and hgroup.
      1. Progress was made, the use counters look quite high though. Will wait a month till they hit stable and reconsider.
   5. On reportError(), undefined, and ErrorEvent Anne will do the spec PR and tests. Olli and Mason will do implementation work.
      1. Spec and test changes landed and all implementations followed (Chromium change landed after the meeting).
   6. Domenic will ping Chromium engineers to comment on Define OffscreenCanvasRenderingContext2D.font setter in detail. Emilio will work on a concrete proposal.
      1. Domenic hasn't received any responses yet. Emilio will work on the proposal soon.
   7. Justin/Mason will add a comment to the Scoped Custom Element Registries issue.
      1. Need feedback from WebKit due to their different memory management. Mason will comment on this.
   8. Chris will follow up with some people and ask them to write a PR for <dialog> initial focus proposal.
      1. Joey left several comments on related issues. Interested parties are encouraged to comment on these issues. Domenic will comment on the individual blockers with his opinion on how blocking/non-blocking they are toward further progress.
2. Carryovers from last time
   1. [Emilio] Proposal: extend FocusOptions to allow specifying :focus-visible behavior
      1. Everyone in support, Emilio will work on a PR and tests.
   2. [Anne] Rendering of "bitmaprenderer"-backed canvas
      1. Will discuss when Anne is back.
3. New topics
   1. [Joey] Mouse events & disabled form controls
      1. Agreement to proceed with Joey's proposal.
   2. [Joey] Event bubbling on disabled form elements
      1. Joey will add use counters to see potential breakage with adopting Chromium's behavior and decide which compat breakage is more tenable. Kagami will test more scenarios for event target.
   3. [Mason] autocomplete attribute for street-address details
      1. Mason will ensure the updated proposal is posted in the issue.
   4. [Domenic] Alternative times for this meeting to accommodate different time zones? E.g. the current time of 6pm Berlin/1am Tokyo/9am San Francisco one month, and a different 3am Berlin/10am Tokyo/6pm San Francisco the other month.
      1. Domenic will open a new issue with several proposals to consider. Emilio suggested meeting biweekly to keep meeting frequency the same for those who can only attend one of the two alternating times.

Action Items

1. @meyerweb to reply to every unresolved comment on the PR for directionality in the shadow DOM.
2. @emilio will work on a concrete proposal for Define OffscreenCanvasRenderingContext2D.font setter in detail.
3. @mfreed7 will comment on the Scoped Custom Element Registries issue.
4. @domenic will comment on the dialog element individual blockers with his opinion on how blocking/non-blocking they are toward further progress.
5. @emilio will work on a PR and tests for Proposal: extend FocusOptions to allow specifying :focus-visible behavior.
6. @josepharhar will add use counters to see potential breakage with adopting Chromium's behavior for Event bubbling on disabled form elements and decide which compat breakage is more tenable. @saschanaz will test more scenarios for event target.
7. @mfreed7 will ensure the updated proposal is posted in the autocomplete attribute for street-address details issue.
8. @domenic will open a new issue about alternative times for this meeting with several proposals to consider.