TPAC 2023 meeting

[past]

At the triage meeting on June 15 we discussed having a face-to-face meeting during TPAC this year. Since then we have reserved a room for two days and started discussions with other groups for potential joint sessions. I took the action item to file an issue with a proposed agenda, which follows below. This is still an early draft, so please suggest any other topics and meetings that would be a valuable way to spend our time together.

TPAC WHATUP meeting agenda

The WHATWG (Web Hypertext Application Technology Working Group) community will meet at the Technical Plenary (TPAC) 2023 in Seville, Spain the week of 12 September 2023. 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 this year. We have the room available for the full day on Thursday and Friday.

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.

Draft agenda

Thursday

9:30-11:00 Introduction to the meeting and welcome. Discussion around WHATWG processes and how to improve them (e.g. the specification acceptance stages proposal, issue triage frequency and duration, attendance across timezones).
11:30-13:00 Joint session with the OpenUI CG
14:30-16:30 Joint session with the CSSWG
17:00-18:30 Discussion around other HTML topics

Friday

9:30-11:00 Followup HTML discussions from the previous day
11:30-13:00 Joint session with the accessibility group
14:30-16:30 Joint session with the Web Performance WG
17:00-18:30 Regular WHATWG triage

Topics for the joint session with OpenUI

• Selectlist element
• dialog updates based on popover (#3567, #9373)
• [Proposal] Invoker Buttons - allowing popover/dialog and more to be invoked without JS html#9625

Topics for the joint session with CSSWG

• element.reorderchildren
• CSS layers via the link element
• Cross-document view-transitions (“reveal” event)
• [View Transitions] Extend render-blocking to support Document html#9332
• "Single content, multiple renderings" feature for <selectlist> w3c/csswg-drafts#9284

Topics for the HTML session

• element.setHTMLUnsafe and document.parseHTMLUnsafe (explainer, Add setHTMLUnsafe and parseHTMLUnsafe methods html#9538)
• Declarative ShadowDOM (#8759, #5465, #892)
• Define or remove Mutation events (Define mutation events dom#305)
• Should we deprecate dialog.show()? html#9376
• Selection API for Web Components (ED, explainer, getComposedRange() review w3c/selection-api#161, Selection APIs for Shadow DOM WICG/webcomponents#79)
• FedCM Fetch integration

Topics for the Friday HTML session

• Revisit Declarative ShadowDOM with @smaug---- (#8759, #5465, #892)
• Observable API proposal (slides)
• iframe reloading issues (Reparenting iframes without reloading html#5484, Proposal: New method to reorder child nodes dom#891)
• Consider adding a headingoffset attribute html#5033
• Programmatically setting focus navigation start point? html#5326
• Symbols in web content
• Pronunciation
• Form-associated custom elements: being a submit button WICG/webcomponents#814

Topics for the joint session with Web Performance

• Better collaboration and process improvements
• FetchLater status and retrospective
• Compression Dictionaries
• isInputPending
• Scheduling APIs

[smaug----]

I wonder if there should be a joint session with some folks from performance wg, at least in case scheduling API proves to be useful (it is still unclear whether it is) and if that should be merged to HTML spec. Right now it is still WICG draft, but it has been discussed in Perf WG, I believe. There might be also other APIs in Perf WG which are very close to HTML.

[muan]

I'd love to see if we can add the following two issues to the HTML topics. I will also be happy to do short presentations about them. I will be attending in person.

whatwg/html#5033
whatwg/html#5326

[past]

I updated the agenda above with all the proposals I have received so far. Keep them coming!

[mfreed7]

Could you please add WICG/webcomponents#814 to the list?

[josepharhar]

• "selectmenu" has been renamed to "selectlist". It has an explainer here: https://open-ui.org/components/selectlist/
• I think that deprecating dialog.show() doesn't necessarily need to be discussed with openui, although I am interested in discussing it with yall.
• declarative shadowdom has some open PRs and issues we can link to:
  • Add DOMParser option to parse declarative shadow DOM html#8759
  • Add declarative Shadow DOM features html#5465
  • Add declarative Shadow DOM features dom#892

[past]

Updated the agenda with your suggestions, thanks Joey.

[khushalsagar]

Can we add whatwg/html#9332 to the TPAC agenda?

[josepharhar]

• Mutation events seems to have an issue here: Define mutation events dom#305
  • My team is supportive of removing them if possible.
• setHTMLUnsafe/parseHTMLUnsafe has a spec PR here: Add setHTMLUnsafe and parseHTMLUnsafe methods html#9538
  • This PR doesn't implement the new sanitizer options yet
• Some links for selection api for web components:
  • https://w3c.github.io/selection-api/#dom-selection-getcomposedrange
  • https://github.com/mfreed7/shadow-dom-selection
  • getComposedRange() review w3c/selection-api#161
  • Selection APIs for Shadow DOM WICG/webcomponents#79

[keithamus]

I'd like to talk about Invoker Buttons if there is available time

[past]

Updated the agenda with everything proposed up to this point.