Upcoming WHATNOT meeting on 1/25/2024

[past]

What is the issue with the HTML Standard?

Today we held our biweekly triage call (#9993) and I will post the meeting notes there in a bit. The next one is scheduled for January 25, 3pm PST. Note that this is 2 weeks later in an America+APAC 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]

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

Agenda

Attendees: Fernando Serboncini, Olli Pettay, Jean-Philippe Gravel, Mason Freed, Khushal Sagar, Vladimir Levin, Di Zhang, Domenic Denicola, Dan Clark, Chris Harrelson, Shu-Yu Guo, Joey Arhar, Panos Astithas, Marcos Caceres, Chris Wilson, Michael Smith

1. Review past action items
   1. Anne will add WebKit feedback (or find someone to do so) on Don't clip range/checkbox/radio overflow to border box.
      1. Done.
   2. Anne will follow up on <button> and user selection with the WebKit engineers.
      1. Marcos will follow up with WebKit engineers.
   3. Mason will prototype the agreed solution for Opening a dialog as modal, nested inside a popover, causes the whole page to go inert with limited ways for the user to address it.
      1. Work has started.
      2. Domenic points out that there are a few popover spec PRs that are under review that should be prioritized.
         1. Ignore DOM state when hiding popovers if needed #9457 [needs rebasing, has discussion with Igalia but Domenic is unclear on conclusion]
         2. Fix user-agent style rules for top layer transitions #9387 [domenic just pinged now]
         3. Hide all popovers when beforetoggle shows a popover #10015 [got a response yesterday]
   4. Emilio will propose a new spec PR and test for User interacted flag gets set when change events are set, but tests disagree.
      1. In progress (Move where the user-valid/invalid flag is set. #10067)
   5. Sanket will follow up internally to find someone to present A way to disable animation of cancelled drag for editor apps like VS Code at a future meeting.
      1. Dan will follow up internally.
   6. Sanket will update the New attribute to control UA-provided writing assistance PR to behave the same as spellcheck.
      1. PR was updated. Olli asks for more work around styling the suggestions. Consensus in the room to try to land what we have and follow up with additional PRs.
   7. Olli will discuss performance with Henri for [View Transitions] Extend render-blocking to support Document.
      1. Done. It does affect page load performance. Investigating what could be done there. Discussed not emitting a closing tag signal but bundling it with the next opening tag.
      2. Marcos pinged a few people internally.
      3. Vlad asks people to chime in to settle the naming issue of the attribute.
2. Carryovers from last time
   1. Simon to look more into nested interactive content spec behavior, with synthetic click events.
      1. Carry over.
   2. [Anne] Add &nnbsp; entity for U+202F
      1. Carryover till February 22 along with the other tagged issues.
3. New topics
   1. [Di] Rendering <input type=range> vertically and Clarify value direction for elements "progress" and "meter" with vertical writing mode
      1. Di to send a spec PR to update https://html.spec.whatwg.org/multipage/rendering.html#the-input-element-as-a-range-control and https://html.spec.whatwg.org/multipage/rendering.html#the-progress-element-2 and https://html.spec.whatwg.org/multipage/rendering.html#the-meter-element-2 with at least the same level of detail.
   2. [Jean-Philippe] Add a layer and filter interface in the 2D canvas
      1. Marcos will follow up with heycam on WebKit's opinion.
      2. Particularly interested in more opinions on the question raised at Canvas2D layers with filter support #8476 (comment)
      3. Olli will follow up internally to see if Gecko's stance is still "neutral" to this proposal.
   3. [Marcos] Allowing UA to do <source> selection for media element
      1. Domenic asked for some data on the benefits and will get an internal Chromium position. Marcos will follow up with jyavenard to see if there is data on efficiency that they can share. Simon will get the Gecko position on this.
   4. [Shu] Seeking feedback on mini waits on the main thread
      1. No strong objections from anyone in the room. Shu will bring it up with TC39 for further discussions.

Action Items

1. @marcoscaceres will follow up with WebKit engineers on <button> and user selection.
2. @dandclark will follow up internally to find someone to present A way to disable animation of cancelled drag for editor apps like VS Code at a future meeting.
3. @dizhang168 to send a spec PR to update https://html.spec.whatwg.org/multipage/rendering.html#the-input-element-as-a-range-control and https://html.spec.whatwg.org/multipage/rendering.html#the-progress-element-2 and https://html.spec.whatwg.org/multipage/rendering.html#the-meter-element-2 with at least the same level of detail.
4. @marcoscaceres will follow up with @heycam on WebKit's opinion on Add a layer and filter interface in the 2D canvas. @smaug---- will follow up internally to see if Gecko's stance is still "neutral" to this proposal.
5. @domenic will get an internal Chromium position for Allowing UA to do <source> selection for media element. @marcoscaceres will follow up with @jyavenard to see if there is any data on efficiency that they can share. @zcorpan will get the Gecko position on it.