Upcoming WHATNOT meeting on 2/8/2024

[past]

What is the issue with the HTML Standard?

Today we held our biweekly triage call (#10052) and I will post the meeting notes there in a bit. The next one is scheduled for February 8, 1am PST. Note that this is 2 weeks later in an APAC+Europe 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 #10128):

Agenda

Attendees: Emilio Cobos Álvarez, Domenic Denicola, Olli Pettay, Noam Rosenthal, Kagami Rosylight, Peter Van der Beken

1. Review past action items
   1. Marcos will follow up with WebKit engineers on <button> and user selection.
      1. Karl commented.
      2. Not sure what next steps are but, we can assume they'll be handled async?
   2. Dan 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. Hasn't happened yet, carry over
   3. 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.
      1. Yes, PR in progress, under review
   4. Marcos will follow up with heycam on WebKit's opinion on Add a layer and filter interface in the 2D canvas. Olli will follow up internally to see if Gecko's stance is still "neutral" to this proposal.
      1. Olli: still neutral
      2. No followup from WebKit, carry over
   5. Domenic will get an internal Chromium position for Allowing UA to do <source> selection for media element. Marcos will follow up with jya to see if there is any data on efficiency that they can share. Simon will get the Gecko position on it.
      1. Done.
2. Carryovers from last time
   1. Simon to look more into nested interactive content spec behavior, with synthetic click events.
      1. No new progress
   2. [Anne] Add &nnbsp; entity for U+202F
      1. Carryover till February 22 along with the other tagged issues.
3. New topics
   1. [Noam] [View Transition] Event on old Document to set transition state
      1. Naming? pageswap seems to be the room's favorite
      2. Some discussion of what happens if you same-document navigate / cross-document navigate / history traverse during the async period. The intent is at least cross-document navigation and history traverse are blocked. Tests will be written.
   2. [Joey] Stylable <select> element
      1. Most current discussion: <select newstuff> vs. <select><datalist> as the new trigger. Thoughts appreciated.
      2. Emilio asks: can we just remove the parser special case so that <select> works?
      3. Action item for people not in this meeting, e.g. Joey: get data on how many pages would break if we did that.
         1. How to use counter this? Unsure. A very conservative upper bound: how many times the parser special case gets hit. (But, maybe we could remove the special case even if this is high, because the rendering wouldn't change.)
   3. [Domenic] Close dialog elements when the open attribute is removed
      1. Olli: "I think this is fine" (he'll take a look after the meeting)
         1. Did comment. Minor tweak needed to the pr
      2. Emilio: glad that Joey found the time for this, yay
      3. Seems unlikely fixing this will break anything

Action Items

1. @josepharhar to get data on how many pages would break if we removed the parser special case for the Stylable <select> element.

[josepharhar]

@josepharhar to get data on how many pages would break if we removed the parser special case for the #9799.

I added usecounters for <button> and <datalist> in <select> here:
https://chromestatus.com/metrics/feature/popularity#HTMLDatalistInSelect
https://chromestatus.com/metrics/feature/popularity#HTMLButtonInSelect

I will add another one for other tags in <select> here:
https://chromium-review.googlesource.com/c/chromium/src/+/5280597