WHATUP at TPAC 2025: agenda suggestions

[cwilso]

What is the issue with the HTML Standard?

The WHATWG community will meet at the W3C TPAC meeting the week of 10 Nov 2025. 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.

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. The agenda 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.

We have 2 time slots at W3C's TPAC 2025:

1. Tues 11 Nov, 9:45-18:00
2. Thur 13 Nov, 9:00-16:45

In addition, we have a joint meeting with I18n WG and APAWG on Fri 14 Nov, 16:30-18:00.

(Last year's WHATUP meta-issue was whatwg/meta#326.)

[annevk]

I think we should reserve some time for introspection again. Would be good to know what things people would like to see improved, who is interested in helping improve things, and what keeps people from improving things.

[rakina]

I would like to discuss Fetch Retry. Will there be a joint session with WebPerfWG too? I've been told if there's a joint WHATWG-WebPerf WG session, it would be best to discuss it at that time, so that I can get feedback for the overall API shape and also iron out the details on the behavior etc.

[domfarolino]

I would like to put the menu elements proposal on the WHATWG agenda for discussion as well.

[noamr]

I'd like to make progress on #11542 and #11669. Hopefully we'll have a spec PR by TPAC.

[smaug----]

Depending on where we will be with Navigation API spec issues in a couple of weeks, there might be a topic to discuss - how to ensure better match between implementations and the spec. This applies especially to Navigation API, but is a more generic topic. Implementations should follow the spec and not do explicitly something else - if something else is needed (because of webcompat or failing WPTs or such) one should file a spec issue.

Some recent Navigation API spec issues
https://github.com/whatwg/html/issues?q=label%3A%22topic%3A%20navigation%22%20type%3ABug

I guess this is a bit related to annevk's comment.

[foolip]

I'd like to discuss HTML-in-Canvas:

• https://github.com/WICG/html-in-canvas
• HTML-in-Canvas #10650
• Add HTML-in-Canvas APIs #11588

I'm also interested in the declarative out-of-order streaming and APIs for streaming HTML mentioned by @noamr above.

[keithamus]

We'd like to revive #127 - and perhaps discuss more generally a pattern where one-shot events have equivalent promises, as we often see buggy websites with timing issues because they miss a DOMContentLoaded event, or a image load event for example.

[smaug----]

It would be good to decide what to do with ShadowRealms. There are tests testing APIs in ShadowRealms and some specs (at least WebIDL) mentions them, but if ShadowRealms won't happen, things should be cleaned up.

[rakina]

Proposing to add #11743 as well to discuss what is the best way to model such an optimization and how to standardize it.

[bvandersloot-mozilla]

I'd like to talk a bit about <meta name="rating" ...> to provide some context and gauge implementer interest. More context will also be provided in the age-based restriction breakout session on Monday