Re: [w3c/push-api] TPAC 2026 Status Report (Issue #418)

marcoscaceres left a comment (w3c/push-api#418)

**1. Progress in the last 12 months**

@annevk landed all three changes since TPAC 2025: `permissionState()` now queues a task, the RFC 7231 reference now points at RFC 9110, and a note that wrongly implied the order of `subscribe()` steps did not matter is gone. Nothing has landed since 1 December 2025.

**2. Blockers to CR**

Forty issues are open, and #334 has asked about moving to CR since 2021 and never reached a decision. Wide review is also incomplete: the internationalization request, w3c/i18n-request#104, has been open since 2017, and we have never filed a security, privacy or accessibility request. The real blocker is testing. #365 called the directory essentially empty in 2023; since then someone has written a delivery test that encrypts a payload and posts it to the subscription endpoint, so the suite is no longer only surface checks. But that test needs whatever push service the browser hands back, and no browser posts a passing result: Edge runs it and fails all six, and Chrome, Firefox and Safari record nothing at all. Whether that is the engines or the test environment is not something the results can tell us, and settling it is the question I want to put to the group.

**3. Testing plan**

web-platform-tests/push-api holds 9 test files. One delivers a message end to end; the other eight cover subscription, permissions, IDL and encodings. A WebDriver command was floated at TPAC 2023 and nobody has built one.

**4. Next steps, and help wanted**

Two things, and I want the group's view on both at TPAC. First, triage the 40 open issues and decide which actually block CR. Second, decide whether anyone will fund the test infrastructure. If the answer is no, we should say so plainly and stop describing CR as the plan.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/418#issuecomment-5869755448
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/418/5869755448@github.com>