Weekly github digest (WebAppSec specs)

Issues
------
* w3c/webappsec (+2/-0/💬2)
  2 issues created:
  - CSP: Allow precise control of cookies (by sindastra)
    https://github.com/w3c/webappsec/issues/561 
  - New permission to access a resource even when CORS headers are not set in the response (by jarrodek)
    https://github.com/w3c/webappsec/issues/560 

  1 issues received 2 new comments:
  - #432 CSP: Provide a way to restrict domain of document.cookie (2 by sindastra)
    https://github.com/w3c/webappsec/issues/432 [CSP] 

* w3c/webappsec-subresource-integrity (+0/-0/💬3)
  1 issues received 3 new comments:
  - #84 The algorithm for parsing metadata should be described in more detail (3 by baek9, domfarolino)
    https://github.com/w3c/webappsec-subresource-integrity/issues/84 

* w3c/webappsec-csp (+0/-1/💬2)
  1 issues received 2 new comments:
  - #7 CSP: connect-src 'self' and websockets (2 by MoxxiManagarm, mikewest)
    https://github.com/w3c/webappsec-csp/issues/7 [CSP] 

  1 issues closed:
  - CSP: connect-src 'self' and websockets https://github.com/w3c/webappsec-csp/issues/7 [CSP] 

* w3c/permissions (+0/-0/💬2)
  1 issues received 2 new comments:
  - #194 Consider making `request-permission-to-use` aware of user activation (2 by beaufortfrancois, dbaron)
    https://github.com/w3c/permissions/issues/194 

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

* w3c/webappsec-fetch-metadata (+0/-1/💬4)
  2 issues received 4 new comments:
  - #51 Header name "destination" may confuse developers (2 by dveditz, jugglinmike)
    https://github.com/w3c/webappsec-fetch-metadata/issues/51 
  - #45 Naming for new items in `mode`. (2 by jugglinmike)
    https://github.com/w3c/webappsec-fetch-metadata/issues/45 

  1 issues closed:
  - Header name "destination" may confuse developers https://github.com/w3c/webappsec-fetch-metadata/issues/51 



Pull requests
-------------
* w3c/webappsec-subresource-integrity (+0/-0/💬3)
  1 pull requests received 3 new comments:
  - #86 Apply integrity checks to inline script and style blocks. (3 by mikewest, mozfreddyb)
    https://github.com/w3c/webappsec-subresource-integrity/pull/86 


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/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-feature-policy
* https://github.com/w3c/webappsec-fetch-metadata
* https://github.com/WICG/trusted-types
* https://github.com/w3c/webappsec-unofficial-drafts