Weekly github digest (WebAppSec specs)

Issues
------
* w3c/webappsec (+1/-0/💬5)
  1 issues created:
  - Planning the 2023-01-18 call. (by mikewest)
    https://github.com/w3c/webappsec/issues/617 

  1 issues received 5 new comments:
  - #617 Planning the 2023-01-18 call. (5 by mikewest, mozfreddyb, tomvangoethem)
    https://github.com/w3c/webappsec/issues/617 

* w3c/webappsec-subresource-integrity (+0/-0/💬7)
  1 issues received 7 new comments:
  - #22 Consider shared caching (7 by alexshpilkin, annevk, brillout, mozfreddyb)
    https://github.com/w3c/webappsec-subresource-integrity/issues/22 

* w3c/webappsec-mixed-content (+2/-0/💬11)
  2 issues created:
  - Why do we not upgrade when a request's initiator is `imageset`? (by mozfreddyb)
    https://github.com/w3c/webappsec-mixed-content/issues/64 
  - Difference between spec and practice in mixed content upgrade  (by moztomer)
    https://github.com/w3c/webappsec-mixed-content/issues/63 

  3 issues received 11 new comments:
  - #64 Why do we not upgrade when a request's initiator is `imageset`? (3 by annevk, estark37, mozfreddyb)
    https://github.com/w3c/webappsec-mixed-content/issues/64 
  - #63 Difference between spec and practice in mixed content upgrade  (5 by annevk, mikewest, moztomer)
    https://github.com/w3c/webappsec-mixed-content/issues/63 
  - #17 Clarify mixed content behavior for access to origins in CIDR 127.0.0.0/8 or ::1/128  (3 by annevk, mikewest)
    https://github.com/w3c/webappsec-mixed-content/issues/17 

* w3c/webappsec-permissions-policy (+2/-1/💬1)
  2 issues created:
  - can anyone help me? (by pollokyoungteam)
    https://github.com/w3c/webappsec-permissions-policy/issues/504 
  - can anyone help me (by pollokyoungteam)
    https://github.com/w3c/webappsec-permissions-policy/issues/503 

  1 issues received 1 new comments:
  - #276 Clarify definition of 'autoplay' policy (1 by krystian3w)
    https://github.com/w3c/webappsec-permissions-policy/issues/276 [feature question] 

  1 issues closed:
  - can anyone help me? https://github.com/w3c/webappsec-permissions-policy/issues/504 



Pull requests
-------------
* w3c/webappsec-mixed-content (+1/-0/💬3)
  1 pull requests submitted:
  - spec: clarify literal ip addresses behaviour (by paulsemel)
    https://github.com/w3c/webappsec-mixed-content/pull/62 

  1 pull requests received 3 new comments:
  - #62 Clarify behaviour for literal IP addresses (3 by annevk, paulsemel)
    https://github.com/w3c/webappsec-mixed-content/pull/62 


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