- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 11 Feb 2019 17:00:23 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1gtEwR-0005uK-0C@uranus.w3.org>
Issues ------ * w3c/webappsec (+1/-0/💬1) 1 issues created: - What about Same-Origin Resource Sharing? (by pak0s) https://github.com/w3c/webappsec/issues/546 1 issues received 1 new comments: - #544 CSP and HTML Modules (1 by shhnjk) https://github.com/w3c/webappsec/issues/544 * w3c/webappsec-subresource-integrity (+0/-0/💬1) 1 issues received 1 new comments: - #20 Consider integrity check violation reporting (1 by rcbarnett) https://github.com/w3c/webappsec-subresource-integrity/issues/20 * w3c/webappsec-csp (+1/-1/💬3) 1 issues created: - Evaluate service-workers mode for CSP violation reports (by cvazac) https://github.com/w3c/webappsec-csp/issues/383 2 issues received 3 new comments: - #383 Evaluate service-workers mode for CSP violation reports (2 by cvazac, wanderview) https://github.com/w3c/webappsec-csp/issues/383 - #125 Allow navigation to only whitelisted URLs via navigate-to (1 by andypaicu) https://github.com/w3c/webappsec-csp/issues/125 1 issues closed: - Evaluate service-workers mode for CSP violation reports https://github.com/w3c/webappsec-csp/issues/383 * w3c/webappsec-mixed-content (+1/-0/💬0) 1 issues created: - "strict mixed content checking flag" not defined for environment settings objects (by annevk) https://github.com/w3c/webappsec-mixed-content/issues/18 * w3c/permissions (+1/-0/💬0) 1 issues created: - Conditional permissions (by martinthomson) https://github.com/w3c/permissions/issues/189 * w3c/webappsec-feature-policy (+1/-0/💬5) 1 issues created: - Scope of speaker policy (by triblondon) https://github.com/w3c/webappsec-feature-policy/issues/275 4 issues received 5 new comments: - #189 Proposal: define default for all (2 by ExE-Boss, triblondon) https://github.com/w3c/webappsec-feature-policy/issues/189 - #193 Feature Policy: lazyload (1 by Malvoz) https://github.com/w3c/webappsec-feature-policy/issues/193 [proposed feature] - #274 Allowing cases where document.write is "ok" (1 by triblondon) https://github.com/w3c/webappsec-feature-policy/issues/274 - #163 Proposal: Parameterized features (1 by triblondon) https://github.com/w3c/webappsec-feature-policy/issues/163 Pull requests ------------- * w3c/webappsec-secure-contexts (+1/-1/💬4) 1 pull requests submitted: - Use WindowOrWorkerGlobalScope as a mixin (by foolip) https://github.com/w3c/webappsec-secure-contexts/pull/64 1 pull requests received 4 new comments: - #64 Use WindowOrWorkerGlobalScope as a mixin (4 by foolip, mikewest, annevk) https://github.com/w3c/webappsec-secure-contexts/pull/64 1 pull requests merged: - Use WindowOrWorkerGlobalScope as a mixin https://github.com/w3c/webappsec-secure-contexts/pull/64 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
Received on Monday, 11 February 2019 17:00:25 UTC