W3C home > Mailing lists > Public > public-webappsec@w3.org > February 2019

Weekly github digest (WebAppSec specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 25 Feb 2019 17:00:21 +0000
To: public-webappsec@w3.org
Message-Id: <E1gyJc5-00046A-5V@uranus.w3.org>



Issues
------
* w3c/webappsec (+0/-2/💬1)
  1 issues received 1 new comments:
  - #543 Prevent programmatic focus in iframe (1 by dveditz)
    https://github.com/w3c/webappsec/issues/543 

  2 issues closed:
  - What about Same-Origin Resource Sharing? https://github.com/w3c/webappsec/issues/546 
  - Prevent programmatic focus in iframe https://github.com/w3c/webappsec/issues/543 

* w3c/webappsec-subresource-integrity (+0/-0/💬5)
  2 issues received 5 new comments:
  - #44 Extend SRI to support integrity metadata on inline script/style blocks (4 by annevk, jhabdas)
    https://github.com/w3c/webappsec-subresource-integrity/issues/44 
  - #21 Consider integrity enforcement of iframe (1 by murbard)
    https://github.com/w3c/webappsec-subresource-integrity/issues/21 

* w3c/webappsec-clear-site-data (+0/-0/💬3)
  1 issues received 3 new comments:
  - #56 [Q] What happens when "executionContexts" is present along with Location header? (3 by julienw, annevk)
    https://github.com/w3c/webappsec-clear-site-data/issues/56 

* w3c/webappsec-feature-policy (+3/-0/💬15)
  3 issues created:
  - Proposal: Define new feature types (by clelland)
    https://github.com/w3c/webappsec-feature-policy/issues/282 
  - Policy proposal for unsolicited-permission-request (by triblondon)
    https://github.com/w3c/webappsec-feature-policy/issues/281 
  - Feature Policy: Service Worker fetch handling (by kinu)
    https://github.com/w3c/webappsec-feature-policy/issues/280 

  7 issues received 15 new comments:
  - #273 Prevent programmatic focus in iframe (5 by frivoal, marian-r, dveditz)
    https://github.com/w3c/webappsec-feature-policy/issues/273 [proposed feature] 
  - #282 Proposal: Define new feature types (4 by annevk, martinthomson, triblondon, clelland)
    https://github.com/w3c/webappsec-feature-policy/issues/282 
  - #163 Proposal: Parameterized features (2 by RByers, triblondon)
    https://github.com/w3c/webappsec-feature-policy/issues/163 
  - #211 [Proposal] Priority hints policy (1 by Malvoz)
    https://github.com/w3c/webappsec-feature-policy/issues/211 [proposed feature] 
  - #244 Maintain a registry (1 by triblondon)
    https://github.com/w3c/webappsec-feature-policy/issues/244 
  - #281 Policy proposal for unsolicited-permission-request (1 by annevk)
    https://github.com/w3c/webappsec-feature-policy/issues/281 
  - #252 Define the scope of feature policy (1 by clelland)
    https://github.com/w3c/webappsec-feature-policy/issues/252 



Pull requests
-------------
* w3c/webappsec-csp (+1/-0/💬1)
  1 pull requests submitted:
  - Spec the form of the report body delivered to the Reporting API. (by paulmeyer90)
    https://github.com/w3c/webappsec-csp/pull/385 

  1 pull requests received 1 new comments:
  - #385 Spec the form of the report body delivered to the Reporting API. (1 by paulmeyer90)
    https://github.com/w3c/webappsec-csp/pull/385 


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, 25 February 2019 17:00:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 February 2019 17:00:27 UTC