Upcoming HTML standard issue triage meeting on 6/2/2022

[past]

Last week we held our monthly triage call (#7802) and I will post the meeting notes there in a bit. The next one is scheduled for June 2, 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.

[mfreed7]

@past, is it possible to get this issue (WICG/webcomponents#716) on the agenda for Thursday? It isn't a whatwg issue, but we'd like to get some eyes on it.

@justinfagnani

[past]

Sure thing, I added it to the agenda.

[past]

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

Agenda

1. Review past action items
   1. XML MIME types used for documents are not interoperable: Anne to figure out whether Firefox wants to align with Chromium/WebKit, or whether he has a proposed alternative processing model.
      1. No progress since last time.
   2. Valid/Invalid characters in document.createElement(): Domenic to write a spec PR
      1. PR is under review. Discussed parser behavior for the equals character. Agreed to disallow it everywhere.
   3. PR for directionality in the shadow DOM: Eric to finish PR. Olli to review PR in addition to Anne.
      1. [Olli] went through the PR. Looks like there are several unresolved comments. Would help if those were addressed and then another review could be done.
      2. Eric to reply to every unresolved comment and then Olli will take another look.
   4. Exposing back/forward cache blocking reasons to sites: Olli to comment on the repo about eviction, not just preventing-going-into-bfcache.
      1. Olli commented, Fergal asked for further clarifications, discussion continues.
   5. Recommend iframe/img over embed/object for some content types: Domenic to work on a PR to documentation-deprecate these elements as much as possible.
      1. No progress since last time.
   6. Inert subtree section is missing requirement that it should NOT be exposed to accessibility: Scott O'Hara seems to be working on authoring guidance. We also need to update Core AAM (?) to state the actual accessibility mapping; unclear who will do that.
      1. Scott commented.
      2. HTML should make sure to link any attributes with a11y guidance to HTML-AAM. (inert="", disabled="", maybe hidden="", maybe future popup=""?). Domenic will file an issue.
   7. Canvas2D Filters: Fernando and his team to work on layer proposal, and rename existing tests to .tentative. Domenic and Anne to discuss whether to revert the PR entirely or keep some of the editorial cleanups or…
      1. No discussions since last time, best would be to revert and move the tests to a tentative directory.
      2. AI: Domenic and Anne to merge the revert to the spec, Domenic to send a PR to move the tests.
   8. inert on an ancestor of modal dialog: Emilio to work on spec PR to align on Gecko/WebKit behavior. This might involve using the new :modal pseudo-class and UA style rules, for both <dialog> and inert="".
      1. Done.
2. Carryovers from last time
   1. [Simon] Remove UA style for h1-h6 in section (et. al.) and hgroup
      1. Mason will take a look.
   2. [Anne] reportError(), undefined, and ErrorEvent
      1. Consensus on following option 1. Anne will do the spec PR and tests. Olli and Mason to do implementation.
   3. [Emilio] Define OffscreenCanvasRenderingContext2D.font setter in detail
      1. Domenic will ping Chromium engineers to comment. Emilio will work on a concrete proposal.
   4. [Emilio] Proposal: extend FocusOptions to allow specifying :focus-visible behavior
      1. Didn't have time for this.
   5. [Anne] Rendering of "bitmaprenderer"-backed canvas
      1. Didn't have time for this.
3. New topics
   1. [Mason] Scoped Custom Element Registries
      1. Open questions to review. This issue discusses moving elements around. Justin/Mason will add a comment to the issue.
   2. [Chris] <dialog> initial focus proposal (originating from this discussion).
      1. Chris will follow up with some people and ask them to write a PR.

Action Items

1. @meyerweb to reply to every unresolved comment on the PR for directionality in the shadow DOM and then @smaug---- will take another look.
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.
3. @domenic and @annevk to merge the Canvas2D Filters revert to the spec, @domenic to send a PR to move the tests.
4. @mfreed7 will take a look at Remove UA style for h1-h6 in section (et. al.) and hgroup.
5. On reportError(), undefined, and ErrorEvent @annevk will do the spec PR and tests. @smaug---- and @mfreed7 will do implementation work.
6. @domenic will ping Chromium engineers to comment on Define OffscreenCanvasRenderingContext2D.font setter in detail. @emilio will work on a concrete proposal.
7. @justinfagnani and @mfreed7 will add a comment to the Scoped Custom Element Registries issue.
8. @chrishtr will follow up with some people and ask them to write a PR for <dialog> initial focus proposal.