admin
admin copied to clipboard
WICG
TPAC 2025
Hi Everyone,
We would like to request a discussion slot at TPAC 2025 for the Text Detection API.
The discussion would primarily focus on WICG/shape-detection-api#109, but we would also like to cover other potential enhancements to the API if time allowed. Is this the correct place to begin the arrangements?
Explainer for WICG/shape-detection-api#109
Pinging @yoavweiss for guidance.
Thanks!
Hey @alvinjiooo ! Noted! (and thanks for kicking off this issue)
@cwilso @liminzhu - let's use this issue to gather requests for F2F meeting time at TPAC
I would like to get more inputs on Fetch Retry (https://github.com/WICG/proposals/issues/217) to hopefully decide on a final shape for it in TPAC, but I'm not quite sure if it should be in the WICG session, a breakout session, or groups like WebPerf or WHATWG (there's lots of discussions in the latter's repo). Is there guidance on this?
I would like to get more inputs on Fetch Retry (https://github.com/WICG/proposals/issues/217) to hopefully decide on a final shape for it in TPAC, but I'm not quite sure if it should be in the WICG session, a breakout session, or groups like WebPerf or WHATWG (there's lots of discussions in the latter's https://github.com/whatwg/fetch/issues/1838). Is there guidance on this?
Given how closely fetch retry relates to existing WHATWG specs and features, I would lean towards the WHATWG agenda or a separate breakout session (pinging the relevant WHATWG experts to hopefully join). Which one you choose depends on what you're trying to get out of TPAC.
If you have a longer presentation where you're trying to sell the proposal to the wider community and get potential partner feedback on the overall idea, then the breakout session sounds good. If that part is in place, and you're trying to make progress on specific technical questions and get spec editor buy-in, and nail down the answers to processing model and edge case questions, then getting on the WHATWG agenda seems right.
My colleagues have recently posted three proposals. It would be great to introduce them and get some feedback.
- Scrollbar Avoidance Area (CSS property) [explainer]
- Speculation Rules API with Additional Headers [explainer]
- Maximum Fling Speed [explainer]
Hello, I am working on an explainer to enable self-js-profiling API in Workers (https://github.com/WICG/js-self-profiling/issues/33), would like to talk and get feedback.
- Document-Policy in Workers - explainer
Hi Everyone,
We would like to request a discussion slot at TPAC 2025 for the Text Detection API.
The discussion would primarily focus on WICG/shape-detection-api#109, but we would also like to cover other potential enhancements to the API if time allowed. Is this the correct place to begin the arrangements?
Pinging @yoavweiss for guidance.
Thanks!
If possible, we wish to have Text Detection API discussion in the afternoon past 12pm JST so we can get a chance to attend Devices & Sensor WG discussion for Geolocation API (also on Nov 13th from 9 - 12 pm JST). Thanks!
Thanks everyone for adding agenda topics for TPAC! The chairs will review them next week and get back to you all on scheduling details during TPAC. I expect we have time for all the topics we have so far, and we will send some guidelines for champions to drive discussion during TPAC. The time block for WICG is on Thursday local time.
In the meantime, if you have known interested parties or partners for your topic, give them a heads up so that they can join and participate in discussions as well.
Below is the current agenda and timetable compiled by chairs for TPAC (event link). Please use WICG TPAC 2025 Meeting Notes for capturing minutes.
| Slot (in JST) | Topic | Champions |
|---|---|---|
| 10:00 - 10:30 | Document policy to enable self-js-profiling API in Worker | @monica-ch |
| 10:30 - 11:00 | Break | |
| 11:00 - 12:15 | Scrollbar Avoidance Area (CSS property) & Speculation Rules with Additional Headers & Maximum Fling Speed | @espinr |
| 12:15 - 1:45 | Lunch | N/A |
| 1:45 - 2:30 | Text Detection API | @alvinjiooo |
Some rough guidelines for TPAC discussion:
- Champions are expected run and drive their respective discussions.
- Please make sure there is someone to capture minutes in WICG TPAC 2025 Meeting Notes for each discussion (recommend champions to bring someone with you if possible; otherwise ask for help in the room).
- Be sure to invite known interested parties to the room/call.
- Liberally use the hand raising feature in Zoom for queue.
- Be nice to each other and follow W3C Code of Ethics and Professional Conduct.
edit - added link for minutes
@monica-ch @espinr @alvinjiooo let me know if this slotting doesn't work for you for any reason and if you have questions. @rakina Chris Wilson is trying to see if your topic can fit in WHATWG's agenda.
FYI I edited https://github.com/WICG/admin/issues/204#issuecomment-3492946781 above to include a google doc for minutes we can all use.
Apologize for some quick last minute timeline update in order to accommodate a common 1030-11:00 break. We will start at 10am. @monica-ch I moved your session from starting at 10:30 to at 10. @espinr I moved yours from starting at 11:15 to at 11. Let me know if this doesn't work.