Upcoming WHATNOT meeting on 12/14/2023

[past]

What is the issue with the HTML Standard?

Today we held our biweekly triage call (#9937) and I will post the meeting notes there in a bit. The next one is scheduled for December 14, 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 #9993):

Agenda

Attendees: Olli Pettay, Sanket Joshi, Vladimir Levin, Mason Freed, Di Zhang, Joey Arhar, Panos Astithas, Marcos Caceres, Chris Harrelson, Chris Wilson

1. Review past action items
   1. David will post more context about weird behavior in the :active and activating via the keyboard issue
      1. Done.
   2. Mason will summarize the consensus in the Add getInnerHTML() that optionally serializes declarative Shadow DOM issue
      1. Done (and done).
   3. Anne will add a comment to autocomplete tokens for EID and IMEI explaining the ways a general purpose browser and website can use this feature to help some set of users
      1. Done.
2. Carryovers from last time
   1. Simon to look more into nested interactive content spec behavior, with synthetic click events.
      1. Carryover.
3. New topics
   1. [Emilio] [forms] Make magic clip not magic
      1. Mason and Marcos will review the issue.
   2. [Noam] [View Transitions] Extend render-blocking to support Document
      1. Olli will comment on the issue. Noam will create a spec PR for this.
      2. (related tech for triggering on close tags here)
   3. [Sanket] Autocomplete on 'contenteditable' Elements
      1. The current proposal is not to modify autocomplete, but add a global property. Olli will update the topic. Marcos says that WebKit is interested in this too. Discussed the use case where platform predictive text conflicting with the websites' autocomplete and the need to have a way that developers can turn it off. Discussed similarities with spell-checking, auto-capitalize, etc.
      2. Sanket will write up a spec PR.
   4. [Joey] Should <button> have user-select: none; by default?
      1. Joey will talk to other Chrome engineers to figure out the reasons behind Blink's behavior. Vladimir pointed out the interaction with select-all and not seeing the contents of a button selected. Sanket pointed out that there is also <input type=submit> to consider if we are aiming for consistency. Blink is open to exploring how to align with Firefox's behavior. Marcos will ask around for WebKit's appetite for a similar change.
   5. [Anne] Add &nnbsp; entity for U+202F
      1. Carryover.
   6. [Panos] Canceled the December 28 meeting. See you again on January 11!

Action Items

1. @mfreed7 and @marcoscaceres will review [forms] Make <input type=button> magic clip not magic.
2. @smaug---- will comment on [View Transitions] Extend render-blocking to support Document. Noam will create a spec PR for this.
3. @sanketj will write up a spec PR for Autocomplete on 'contenteditable' Elements.
4. @josepharhar will talk to other Chrome engineers to figure out the reasons behind Blink's behavior around <button> and user selection. @marcoscaceres will ask around for WebKit's appetite for a similar change.