TPAC 2024 WHATUP meeting agenda

The WHATWG (Web Hypertext Application Technology Working Group) community will meet at the Technical Plenary (TPAC) 2024 in Anaheim, CA USA the week of 23 September 2024. We call this the "Web HyperText Application Technology Unconference Plenary" or WHATUP for short. See the overall meeting page for conference, hotel, and travel logistics. Registration is required.

Remote participation is available via Zoom. People who can are encouraged to attend as the face to face opportunity is valuable for the work, but W3C expects many people to be unable to attend and plans to provide quality remote participation support. Note that registration is required for remote participants.

The purpose of this meeting is to make progress on the current open tasks in a high-bandwidth medium that an in-person meeting provides. Additionally it will be an excellent opportunity to strengthen the relationships between all participants by spending some time together after a long time. There is a draft agenda below, but it will become more concrete closer to TPAC, when it becomes clear what issues have been resolved and what new topics have come up.

Please suggest topics in the comments below and I will incorporate them in the agenda.

Schedule

Monday

14:00-16:00 Joint meeting with the CSS Working Group

Tuesday

9:00-12:30 Joint meeting with the CSS Working Group and the OpenUI Community Group
16:30-18:00 Regular WHATWG triage

Thursday

11:00-12:30 Joint meeting with the Accessible Platform Architectures Working Group

Friday

14:00-16:00 Joint meeting with the Web Performance Working Group
16:30-18:00 Joint meeting with the Internationalization Working Group

Agenda

Topics for the joint session with the CSSWG

• Expand blocking=render to blocking="view-transition" (Consider adding view-transition as a token for blocking html#10513 )
• Reading flow
  • https://github.com/w3c/csswg-drafts/issues/9230 (overall proposal)
  • https://github.com/whatwg/html/issues/10407 (overall proposal)
  • Discussing how to focus navigate display: contents elements that are focusable in CSS reading-flow html#10533 (display:contents issue)
  • https://drafts.csswg.org/css-display-4/#reading-flow
  • Add support for CSS reading-flow html#10613

Topics for the joint session with the OpenUI & CSS WGs

• customizable <select>
  • <select> UA stylesheet: [css-ui] UA stylesheet for appearance:base <select> w3c/csswg-drafts#10857
  • <select> content model: Content model and 'what' to render for stylable <select> elements html#10317
  • [css-forms-1] Define design principles for appearance: base stylesheet w3c/csswg-drafts#10866
  • [css-ui] Pseudo-elements for checkmark and dropdown icon for appearance:base <select> w3c/csswg-drafts#10908
  • [css-ui] Colors to use for appearance:base <select> w3c/csswg-drafts#10909
• Tooltips, Hovercards, and Menus
  • Overview presentation
  • Popover=hint: Add popover=hint html#9778
  • Invoker buttons: Add commandfor & command attributes to HTMLButtonElement html#9841 and [Proposal] Invoker Buttons - allowing popover/dialog and more to be invoked without JS html#9625
  • Interest invokers: https://open-ui.org/components/interest-invokers.explainer/
  • [interest invokers] Touch inputs openui/open-ui#1052 (touch support)
  • Extend popovertarget to support custom elements openui/open-ui#1088
• Rich Inputs explainer openui/open-ui#1090

Topics for the WHATWG session

• Atomic move operation (moveBefore) Atomic move operation for element reparenting & reordering dom#1255
  • Agenda doc
• Observable API https://github.com/WICG/observable
  • Agenda doc
• Provide an API for getting visible caret position in textarea/input element html#10614
• Companion Windows
• Prevent programmatic focus in iframe w3c/webappsec-permissions-policy#273 (PR: Feature Policy: focus-without-user-activation html#4585)
• PlaceElement WICG (https://github.com/WICG/canvas-place-element): Moving to Stage 1, we are going to have biweekly meetings, with browser representation. How can we move it forward while still keeping WHATWG in the loop? Can an editor participate in it?
  • HTML-in-Canvas html#10650
• Merging Canvas Layer PR: Add a layer and filter interface in the 2D canvas html#9537
• Enhanced TextMetrics (https://github.com/fserb/canvas2D/blob/master/spec/enhanced-textmetrics.md): most of this has been presented before, except for TextCluster. We would like some feedback on it. We are ready to move forward with a PR.
• Canvas WebGL/WebGPU Transfer (https://github.com/fserb/canvas2D/blob/master/spec/webgpu.md) this spec allows to switch a Canvas 2D into a WebGL/WebGPU texture and back into the backing buffer. We would like to present the API, grab feedback, and discuss how we can move forward with it since it involves both WHATWG and WebGL/WebGPU.
• customizable <select>
  • Timing of cloning for the <selectedoption> element html#10520 (Clone timing)
  • Content model and 'what' to render for stylable <select> elements html#10317 (Content model)

Topics for the joint session with the Accessible Platform Architectures WG

• ARIA attribute reflection
• Symbols - we would like to address present technical questions/blocks regarding authoring considerations.
• Well-known destinations - we would like your views on the best way to proceed with this spec: we currently have two potential routes to implementation.

Topics for the joint session with the Web Performance WG

• Consolidating fetchLater (Request Limit WICG/pending-beacon#87, Deferred fetching fetch#1647 )
• Scheduling API updates
• Compression Streams
  • zstd and brotli. Is it acceptable to add support only for decompression?
  • Design of the options bag

Topics for the joint session with the Internationalization WG

• Input type=email (Validating internationalized mail addresses in <input type="email"> html#4562)
• Topic: Locale and language tag related issues
  • Proposal for Element.currentLang and Element.currentDir html#7039
  • Making input respect locale (which is quasi-in-the-spec, but inconsistently implemented)
  • Fixing <time> and potentially having locale-aware presentational elements.
• Topic: Bidi issues
  • Bidi issues
  • Should dir=auto with no strong characters inherit directionality from parent or be ltr? w3c/i18n-activity#1819
• Topic: date/time related issues and locale-sensitivity in general
  • time related issues
  • Agenda+ full list