Upcoming HTML standard issue triage meeting on 9/1/2022 (new time!)

[past]

Today we held our monthly triage call (#8162) and I will post the meeting notes there in a bit. The next one is scheduled for September 1, 1 am PDT, per #8106. Note that this is 2 (not 4) weeks later in an APAC+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]

I have updated the agenda for this meeting and it seems a bit sparse, so feel free to tag more issues/PRs for discussion.

[past]

On a scheduling note, it looks like our next HTML triage meeting conflicts with TPAC. I'm thinking of skipping this instance and meeting in 4 weeks, unless others disagree.

[past]

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

Agenda

1. Review past action items
   1. Someone else will have to chair the meeting next time. Domenic volunteered.
      1. Done.
   2. Eric to respond to Olli's review feedback in the PR for directionality in the shadow DOM.
      1. No updates
   3. Emilio/Domenic/someone should figure out if there is test coverage for focus delegate code seems wrongly only looking at children.
      1. Emilio will make sure the Gecko patch includes enough test coverage, then we can merge!
   4. Domenic will comment on the Clarify UX (keyboard) and further a11y expectations for modeless dialogs thread.
      1. Done.
2. Carryovers from last time
   1. [Anne] Rendering of "bitmaprenderer"-backed canvas
      1. Anne to check with WebKit canvas people, post an update, ideally including a concrete proposal for a spec change everyone can converge on.
   2. Emilio will work on a concrete proposal for Define OffscreenCanvasRenderingContext2D.font setter in detail.
      1. Still on Emilio's to-do list. Some updates from mysteryDate about out-of-document elements, and he seems to be signaling agreement with Emilio's direction. Emilio can try to instead push mysteryDate to do the work since he volunteered!
3. New topics
   1. [Anne] Allow more characters in dataset?
      1. General agreement we should do this
   2. [Domenic] Define timing of focus fixup rule precisely when triggered by style changes
      1. Tentative consensus. Domenic to do spec work, Emilio to update tests.
      2. However, we're unsure where to fit this in inside update the rendering. After substep 16?? That'd be quite novel, but would avoid having to update layout in an intermediate place. We're pretty sure doing it right before 16 is observably equivalent to right after 16; need to investigate. Probably after 13 (rAF). And maybe add a note so we know how to do this in the future.
         1. Define concepts of batching and flushing of style and layout information w3c/csswg-drafts#5115 is the relevant csswg issue fwiw.
   3. [Domenic] Define link processing for prefetch
      1. Carryover
   4. APA & WHAT-WG Open Issues Joint Meeting (TPAC Tuesday 4PM local time)
      1. Just a heads up

Action Items

1. @emilio will make sure the Gecko patch for focus delegate code seems wrongly only looking at children includes enough test coverage.
2. @annevk to check with WebKit canvas people, post an update on Rendering of "bitmaprenderer"-backed canvas, ideally including a concrete proposal for a spec change everyone can converge on.
3. @domenic to do spec work for Define timing of focus fixup rule precisely when triggered by style changes, @emilio to update tests.