Re: [w3c/manifest] TPAC 2026 Status Report (Issue #1240)

marcoscaceres left a comment (w3c/manifest#1240)

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

@christianliebel added the `color_scheme_dark` member and themeable color members (#1207). @dmurph promoted the internationalization appendix to a proper Internationalization Considerations section (#1234). I redefined application context on top of the top-level traversable (#1219), renamed "default display mode" to "applied display mode" (#1215), clarified how a user agent fetches manifest image resources (#1171), split privacy and security considerations into two sections (#1224), and added a recommendation that user agents let people inspect and change shortcut URLs (#1221).

**2. Blockers to CR**

#1225 tracks the transition. We asked for wide review on 6 July 2026 with a 3 August deadline.
Internationalization is engaging: @aphillips filed #1229 and #1230, and @christianliebel drafted the checklist review at #1223. Security (w3c/security-request#139) and privacy (w3cping/privacy-request#217) have not answered at all, and both are now eight weeks past the date we asked for. We have not yet requested TAG or accessibility review.

**3. Testing plan**

web-platform-tests/appmanifest holds 68 tests across 19 per-member directories. One real gap remains, tracked at #1194: anything that depends on the user installing the app cannot be tested today (same problem as badging). I don't think that is a solvable problem.

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

Chase security and privacy, file the TAG and accessibility requests, close the open i18n issues, then run the CfC.

#1247 exports the "applied" dfn so other specs can link the relation between a top-level traversable and the manifest applied to it.


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

Message ID: <w3c/manifest/issues/1240/5868972159@github.com>