- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Mon, 03 Nov 2025 17:00:38 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1vFxv4-00H8Cr-0X@janus.w3.internal>
Issues
------
* w3c/webappsec (+0/-0/💬4)
1 issues received 4 new comments:
- #689 Planning TPAC 2025 (4 by dveditz, simoneonofri)
https://github.com/w3c/webappsec/issues/689
* w3c/webappsec-subresource-integrity (+10/-0/💬1)
10 issues created:
- Integrity for source maps (by mozfreddyb)
https://github.com/w3c/webappsec-subresource-integrity/issues/165 [feature-request]
- Proposed covered resource types (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/164 [waict]
- Support for multiple resources per Hash (Multiple resources in a JS file) (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/163 [waict]
- Manifest Hashes Format (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/162 [waict]
- Multiple Manifests (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/161 [waict]
- Inline Manifest (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/160 [waict]
- WAICT enforcement modes (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/159 [waict]
- Supporting WAICT Manifest in Integrity-Policy (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/158 [waict]
- Script coverage is non-exhaustive (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/157 [waict]
- Integrity-Policy gaps for WAICT (by ezzak)
https://github.com/w3c/webappsec-subresource-integrity/issues/156 [waict]
1 issues received 1 new comments:
- #165 Integrity for source maps (1 by mozfreddyb)
https://github.com/w3c/webappsec-subresource-integrity/issues/165 [feature-request]
* w3c/webappsec-csp (+2/-1/💬0)
2 issues created:
- Broken links in Content Security Policy Level 3 (by dontcallmedom-bot)
https://github.com/w3c/webappsec-csp/issues/789
- Incorrect assertion in Obtain the deprecated serialization of violation (by Lubrsi)
https://github.com/w3c/webappsec-csp/issues/788
1 issues closed:
- Does `strict-dynamic` allow dynamically adding inline scripts? https://github.com/w3c/webappsec-csp/issues/426
* w3c/webappsec-credential-management (+1/-0/💬0)
1 issues created:
- Do we still want willRequestConditionalCreation? (by marcoscaceres)
https://github.com/w3c/webappsec-credential-management/issues/279
* w3c/permissions (+0/-0/💬4)
1 issues received 4 new comments:
- #471 Can permissions.setPermission not use context? (4 by annevk, bvandersloot-mozilla, cfredric)
https://github.com/w3c/permissions/issues/471
* w3c/webappsec-permissions-policy (+1/-0/💬4)
1 issues created:
- Exact behavior for navigating iframes (by simon-friedberger)
https://github.com/w3c/webappsec-permissions-policy/issues/578
1 issues received 4 new comments:
- #578 Exact behavior for navigating iframes (4 by clelland, simon-friedberger)
https://github.com/w3c/webappsec-permissions-policy/issues/578
* w3c/webappsec-fetch-metadata (+1/-1/💬0)
1 issues created:
- Remove (by mandyhart1924-hash)
https://github.com/w3c/webappsec-fetch-metadata/issues/95
1 issues closed:
- Remove https://github.com/w3c/webappsec-fetch-metadata/issues/95
* w3c/webappsec-trusted-types (+0/-0/💬6)
1 issues received 6 new comments:
- #594 Streaming support (6 by annevk, foolip, lukewarlow, noamr)
https://github.com/w3c/trusted-types/issues/594 [enhancement] [spec] [future]
Pull requests
-------------
* w3c/webappsec-csp (+1/-0/💬2)
1 pull requests submitted:
- (by antosart)
2 pull requests received 2 new comments:
- #790 [Editorial] Fix broken references to Trusted Types spec (1 by annevk)
https://github.com/w3c/webappsec-csp/pull/790 [editorial]
- #787 Apply `strict-dynamic` to inline scripts. (1 by mikewest)
https://github.com/w3c/webappsec-csp/pull/787
* w3c/webappsec-credential-management (+3/-0/💬0)
3 pull requests submitted:
- (by marcoscaceres)
- (by marcoscaceres)
- (by marcoscaceres)
* w3c/webappsec-trusted-types (+2/-0/💬2)
2 pull requests submitted:
- (by antosart)
- (by lukewarlow)
2 pull requests received 2 new comments:
- #603 Export the "Does sink type require trusted types?" algorithm (1 by lukewarlow)
https://github.com/w3c/trusted-types/pull/603
- #602 Remove abstract-ops from the spec (1 by lukewarlow)
https://github.com/w3c/trusted-types/pull/602
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webappsec
* https://github.com/w3c/webappsec-subresource-integrity
* https://github.com/w3c/webappsec-csp
* https://github.com/w3c/webappsec-mixed-content
* https://github.com/w3c/webappsec-upgrade-insecure-requests
* https://github.com/w3c/webappsec-credential-management
* https://github.com/w3c/permissions
* https://github.com/w3c/permissions-registry
* https://github.com/w3c/webappsec-referrer-policy
* https://github.com/w3c/webappsec-secure-contexts
* https://github.com/w3c/webappsec-clear-site-data
* https://github.com/w3c/webappsec-cowl
* https://github.com/w3c/webappsec-epr
* https://github.com/w3c/webappsec-suborigins
* https://github.com/w3c/webappsec-cspee
* https://github.com/w3c/webappsec-permissions-policy
* https://github.com/w3c/webappsec-fetch-metadata
* https://github.com/w3c/webappsec-trusted-types
* https://github.com/w3c/webappsec-change-password-url
* https://github.com/w3c/webappsec-post-spectre-webdev
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 November 2025 17:00:39 UTC