- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 14 Jan 2019 17:00:14 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1gj5aw-0003XR-Fo@uranus.w3.org>
Issues ------ * w3c/webappsec-csp (+0/-0/💬2) 1 issues received 2 new comments: - #174 Policy to allow only custom properties in inline CSS (2 by dav-is, dveditz) https://github.com/w3c/webappsec-csp/issues/174 * w3c/webappsec-upgrade-insecure-requests (+0/-0/💬1) 1 issues received 1 new comments: - #14 Should loopback and other trusted urls be upgraded? (1 by ericlaw1979) https://github.com/w3c/webappsec-upgrade-insecure-requests/issues/14 * w3c/webappsec-clear-site-data (+0/-0/💬1) 1 issues received 1 new comments: - #56 [Q] What happens when "executionContexts" is present along with Location header? (1 by annevk) https://github.com/w3c/webappsec-clear-site-data/issues/56 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
Received on Monday, 14 January 2019 17:00:15 UTC