Weekly github digest (WebAppSec specs)

Issues
------
* w3c/webappsec (+0/-0/💬1)
  1 issues received 1 new comments:
  - #664 Provide clear guidelines for what `Timing-Allow-Origin` should expose  (1 by noamr)
    https://github.com/w3c/webappsec/issues/664 

* w3c/webappsec-csp (+1/-0/💬0)
  1 issues created:
  - connect-src test suite allows multiple non-interopable implementations. (by lukewarlow)
    https://github.com/w3c/webappsec-csp/issues/706 

* w3c/webappsec-permissions-policy (+0/-0/💬1)
  1 issues received 1 new comments:
  - #189 Proposal: define default for all (1 by vphantom)
    https://github.com/w3c/webappsec-permissions-policy/issues/189 [feature question] 

* w3c/webappsec-trusted-types (+0/-1/💬1)
  1 issues received 1 new comments:
  - #520 Finalise spec mechanism for event handlers (1 by fred-wang)
    https://github.com/w3c/trusted-types/issues/520 [spec] 

  1 issues closed:
  - Add test for event handler content attribute handling for false positive event handler attributes https://github.com/w3c/trusted-types/issues/573 



Pull requests
-------------
* w3c/webappsec-csp (+1/-0/💬1)
  1 pull requests submitted:
  - Use given CSP list in navigation request checking (by domenic)
    https://github.com/w3c/webappsec-csp/pull/705 

  1 pull requests received 1 new comments:
  - #692 Use "navigation request's policy container's CSP list" instead of "navigation request's client's global object's CSP list" (1 by domenic)
    https://github.com/w3c/webappsec-csp/pull/692 [blocked] 

* w3c/permissions (+1/-0/💬1)
  1 pull requests submitted:
  - Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (by aselya)
    https://github.com/w3c/permissions/pull/458 

  1 pull requests received 1 new comments:
  - #458 Allow for the query algorithm to return `prompt` or `denied` when document is not `allowed to use` (1 by miketaylr)
    https://github.com/w3c/permissions/pull/458 

* w3c/webappsec-permissions-policy (+1/-0/💬0)
  1 pull requests submitted:
  - Add allow and src attribute to potential permissions policy violation report (by shhnjk)
    https://github.com/w3c/webappsec-permissions-policy/pull/559 

* w3c/webappsec-fetch-metadata (+0/-0/💬8)
  1 pull requests received 8 new comments:
  - #89 Define `Sec-Fetch-Frame-Ancestors`. (8 by annevk, bvandersloot-mozilla, ddworken, johannhof, sjledoux)
    https://github.com/w3c/webappsec-fetch-metadata/pull/89 


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