Weekly github digest (WebAppSec specs)

Issues
------
* w3c/webappsec-mixed-content (+0/-1/💬1)
  1 issues received 1 new comments:
  - #77 "Should fetching request be blocked as mixed content?" doesn't look at the request's current URL (1 by mikewest)
    https://github.com/w3c/webappsec-mixed-content/issues/77 

  1 issues closed:
  - "Should fetching request be blocked as mixed content?" doesn't look at the request's current URL https://github.com/w3c/webappsec-mixed-content/issues/77 

* w3c/webappsec-trusted-types (+1/-0/💬1)
  1 issues created:
  - Spec text should define how to match against tt-keyword. (by otherdaniel)
    https://github.com/w3c/trusted-types/issues/604 

  1 issues received 1 new comments:
  - #604 Spec text should define how to match against tt-keyword. (1 by annevk)
    https://github.com/w3c/trusted-types/issues/604 




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, 12 January 2026 17:00:35 UTC