Web Application Security Working Group - Activity in 2022
No matches.
TR publications
-
5 documents published.
-
Permissions published 3 times as a Working Draft. History of Permissions
-
Permissions Policy published as a Working Draft. History of Permissions Policy
-
Content Security Policy Level 3 published as a Working Draft. History of Content Security Policy Level 3
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
gal weizman (Consensys) joined.
-
Chaals Nevile (Consensys) joined.
-
-
1 organization joined.
-
Consensys joined.
-
GitHub
w3c/webappsec-csp
-
1 issue opened.
-
Remove initialization hook w3c/webappsec-csp#581, by @antosart.
-
-
3 issues closed.
-
Directive's value is a set w3c/webappsec-csp#577.
-
Broken references in Content Security Policy Level 3 w3c/webappsec-csp#576.
-
Should we replace browsing contexts with navigables? w3c/webappsec-csp#579.
-
-
3 issues received 3 new comments.
-
CSP 4 Feature Request: add new 'default' keyword to compose default-src sources into other directives w3c/webappsec-csp#321 (1 comment by @chrisgraham)
-
The editor's draft includes several features that no one has shipped. w3c/webappsec-csp#563 (1 comment by @noamr)
-
-
1 pull request opened.
-
Use "least restrictive" directive instead of `prefetch-src` w3c/webappsec-csp#582, by @noamr.
-
-
2 pull requests merged.
-
Fix for each iterations referring to infra w3c/webappsec-csp#578.
-
Fix references to html after navigation and session history rewrite w3c/webappsec-csp#580.
-
-
3 pull requests received 22 new comments.
-
Use "least restrictive" directive instead of `prefetch-src` w3c/webappsec-csp#582 (17 comments by @annevk, @mikewest, @noamr)
-
Fix references to html after navigation and session history rewrite w3c/webappsec-csp#580 (4 comments by @antosart, @domenic)
-
w3c/webcrypto
-
2 issues received 2 new comments.
w3c/webappsec-permissions-policy
-
2 issues opened.
-
Clarify "Shipped in Chrome" for picture-in-picture in features.md w3c/webappsec-permissions-policy#502, by @XSpielinbox.
-
killed my sperm count w3c/webappsec-permissions-policy#500, by @IAN694201010101.
-
-
4 issues closed.
-
killed my sperm count w3c/webappsec-permissions-policy#500.
-
Set up auto-publishing w3c/webappsec-permissions-policy#487.
-
Typo on "allowusermedia" section w3c/webappsec-permissions-policy#153.
-
Proposal: Transition 'document-domain' feature to Document Policy w3c/webappsec-permissions-policy#414.
-
-
4 issues received 6 new comments.
-
Set up auto-publishing w3c/webappsec-permissions-policy#487 (3 comments by @clelland, @sideshowbarker)
-
"Process permissions policy attributes" unclear w3c/webappsec-permissions-policy#489 (1 comment by @clelland)
-
Make GitHub the preferred way to give feedback w3c/webappsec-permissions-policy#427 (1 comment by @clelland)
-
Proposal: Transition 'document-domain' feature to Document Policy w3c/webappsec-permissions-policy#414 (1 comment by @clelland)
-
-
8 pull requests opened.
-
Fix `Define an inherited policy for feature in container at origin` w3c/webappsec-permissions-policy#501, by @arichiv.
-
Update "Is feature enabled in document for origin?" behavior w3c/webappsec-permissions-policy#499, by @xyaoinum.
-
Fixes based on build warnings w3c/webappsec-permissions-policy#498, by @arichiv.
-
Add smart-card w3c/webappsec-permissions-policy#496, by @dandrader.
-
Propose shared-autofill feature w3c/webappsec-permissions-policy#495, by @schwering.
-
Remove old note for enabling Serial w3c/webappsec-permissions-policy#494, by @freddieleeman.
-
Add User-Agent Client Hints ch-ua-* features w3c/webappsec-permissions-policy#493, by @freddieleeman.
-
Remove mailing list from header w3c/webappsec-permissions-policy#492, by @clelland.
-
-
4 pull requests merged.
-
Add local-fonts permission policy w3c/webappsec-permissions-policy#458.
-
Add keyboard-map feature policy. w3c/webappsec-permissions-policy#428.
-
Reference "generate and queue a report" w3c/webappsec-permissions-policy#484.
-
Remove document-domain policy-controlled feature. w3c/webappsec-permissions-policy#491.
-
-
1 pull request closed.
-
Add window-placement to features.md w3c/webappsec-permissions-policy#424.
-
-
1 pull request reopened.
-
Fix `Define an inherited policy for feature in container at origin` w3c/webappsec-permissions-policy#501, by @arichiv.
-
-
7 pull requests received 9 new comments.
-
Remove document-domain policy-controlled feature. w3c/webappsec-permissions-policy#491 (2 comments by @clelland, @otherdaniel)
-
Propose identity-credential-get permission policy w3c/webappsec-permissions-policy#488 (1 comment by @clelland)
-
add experimental features join-ad-interest-group and run-ad-auction w3c/webappsec-permissions-policy#438 (1 comment by @clelland)
w3c/permissions
-
2 issues opened.
-
Fold in Permissions Policy w3c/permissions#410, by @annevk.
-
Permissions.query takes and object, but magically that is converted to a dictionary w3c/permissions#403, by @smaug----.
-
-
2 issues closed.
-
Can we more formally define the "Permission Store" w3c/permissions#384.
-
Permissions.query takes and object, but magically that is converted to a dictionary w3c/permissions#403.
-
-
1 issue reopened.
-
Task queueing w3c/permissions#393, by @marcoscaceres.
-
-
3 issues received 7 new comments.
-
Permissions.query takes and object, but magically that is converted to a dictionary w3c/permissions#403 (2 comments by @annevk, @marcoscaceres)
-
Automation: Need two more steps to handle closed browsing context and user prompts w3c/permissions#347 (1 comment by @marcoscaceres)
-
3 pull requests opened.
-
Export definition of Set Permission extension command w3c/permissions#408, by @dontcallmedom.
-
Export permissions task source w3c/permissions#407, by @johannhof.
-
Editorial: fix PermissionDescriptor name check in query() w3c/permissions#404, by @marcoscaceres.
-
-
4 pull requests merged.
-
Export definition of Set Permission extension command w3c/permissions#408.
-
Define a permission store (closes #384) w3c/permissions#390.
-
Editorial: fix PermissionDescriptor name check in query() w3c/permissions#404.
-
Editorial: define and improve use of permissions task source w3c/permissions#398.
-
-
1 pull request closed.
-
Editorial: user enum values for permission concept w3c/permissions#399.
-
-
9 pull requests received 40 new comments.
-
Define a permission store (closes #384) w3c/permissions#390 (24 comments by @annevk, @johannhof, @jyasskin, @marcoscaceres, @miketaylr)
-
Integrate "request permission to use" with user activation w3c/permissions#401 (5 comments by @annevk, @jyasskin, @marcoscaceres, @miketaylr)
-
Export definition of Set Permission extension command w3c/permissions#408 (3 comments by @dontcallmedom, @marcoscaceres)
-
w3c/permissions#409 (1 comment by @w3cbot)
-
w3c/permissions#406 (1 comment by @w3cbot)
-
w3c/permissions#405 (1 comment by @w3cbot)
-
Editorial: fix PermissionDescriptor name check in query() w3c/permissions#404 (1 comment by @annevk)
-
w3c/webappsec-fetch-metadata
-
1 pull request opened.
-
Define the Sec-Purpose header w3c/webappsec-fetch-metadata#85, by @noamr.
-
-
1 pull request closed.
-
Define the Sec-Purpose header w3c/webappsec-fetch-metadata#85.
-
-
1 pull request received 23 new comments.
-
Define the Sec-Purpose header w3c/webappsec-fetch-metadata#85 (23 comments by @annevk, @domenic, @mikewest, @noamr)
-
w3c/webappsec-mixed-content
-
1 issue opened.
-
Broken references in Mixed Content w3c/webappsec-mixed-content#61, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.
-
Clarify mixed content behavior for access to origins in CIDR 127.0.0.0/8 or ::1/128 w3c/webappsec-mixed-content#17 (1 comment by @annevk)
-
w3c/permissions-registry
-
1 pull request opened.
-
Add local-fonts to table of provisional permissions w3c/permissions-registry#20, by @inexorabletash.
-
-
1 pull request merged.
-
Add local-fonts to table of provisional permissions w3c/permissions-registry#20.
-
-
1 pull request received 5 new comments.
-
Add local-fonts to table of provisional permissions w3c/permissions-registry#20 (5 comments by @inexorabletash, @miketaylr)
-
w3c/webappsec
-
1 issue received 2 new comments.
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Tom Van Goethem (Google LLC) joined.
-
Thomas Nguyen (Google LLC) joined.
-
-
1 participant left.
-
Bradford Lassey (Google LLC) left.
-
GitHub
w3c/permissions
-
6 issues opened.
-
PermissionDescriptor equality is not defined w3c/permissions#396, by @annevk.
-
"permission query algorithm" run on string w3c/permissions#395, by @annevk.
-
"permission query algorithm" is passed a redundant argument w3c/permissions#394, by @annevk.
-
Task queueing w3c/permissions#393, by @annevk.
-
Align internal states with enums w3c/permissions#392, by @annevk.
-
Consider removing "lifetime" w3c/permissions#391, by @annevk.
-
-
1 issue closed.
-
Potentially revisit oneRealm w3c/permissions#387.
-
-
9 issues received 31 new comments.
-
Consider removing "lifetime" w3c/permissions#391 (10 comments by @annevk, @johannhof, @marcoscaceres, @tungnh28)
-
Allow returning "prompt" rather than "denied" w3c/permissions#388 (5 comments by @annevk, @johannhof, @miketaylr)
-
Consider making `request-permission-to-use` aware of user activation w3c/permissions#194 (2 comments by @marcoscaceres)
-
"permission query algorithm" is passed a redundant argument w3c/permissions#394 (1 comment by @jyasskin)
-
-
7 pull requests opened.
-
Add additional automation error checks w3c/permissions#402, by @marcoscaceres.
-
Integrate "request permission to use" with user activation w3c/permissions#401, by @marcoscaceres.
-
Editorial: define permission states consistently w3c/permissions#400, by @marcoscaceres.
-
Editorial: user enum values for permission concept w3c/permissions#399, by @marcoscaceres.
-
Editorial: define and improve use of permissions task source w3c/permissions#398, by @marcoscaceres.
-
Remove use of realms w3c/permissions#397, by @marcoscaceres.
-
Define a permission store (closes #384) w3c/permissions#390, by @johannhof.
-
-
1 pull request merged.
-
Remove use of realms w3c/permissions#397.
-
-
4 pull requests received 77 new comments.
-
Define a permission store (closes #384) w3c/permissions#390 (67 comments by @annevk, @johannhof, @jyasskin, @marcoscaceres, @miketaylr)
-
Integrate "request permission to use" with user activation w3c/permissions#401 (4 comments by @annevk, @marcoscaceres)
-
Editorial: define and improve use of permissions task source w3c/permissions#398 (1 comment by @marcoscaceres)
-
w3c/webappsec
-
1 issue received 2 new comments.
w3c/webappsec-permissions-policy
-
1 issue opened.
-
Update web-platform-tests w3c/webappsec-permissions-policy#490, by @annevk.
-
-
1 issue received 3 new comments.
-
Denying self while still allowing subframes w3c/webappsec-permissions-policy#480 (3 comments by @fergald, @tungnh28)
-
-
1 pull request opened.
-
Remove document-domain policy-controlled feature. w3c/webappsec-permissions-policy#491, by @otherdaniel.
-
-
1 pull request merged.
-
Add Bluetooth to the list of policy-controlled features w3c/webappsec-permissions-policy#476.
-
-
2 pull requests received 6 new comments.
-
Remove document-domain policy-controlled feature. w3c/webappsec-permissions-policy#491 (4 comments by @clelland, @otherdaniel)
-
Add Bluetooth to the list of policy-controlled features w3c/webappsec-permissions-policy#476 (2 comments by @clelland, @w3cbot)
-
w3c/webappsec-fetch-metadata
-
1 issue opened.
-
Define `Sec-Purpose: Prefetch` w3c/webappsec-fetch-metadata#84, by @noamr.
-
w3c/webappsec-subresource-integrity
-
2 issues opened.
-
Reference the IANA registry of hash names w3c/webappsec-subresource-integrity#119, by @jb-wisemo.
-
Check all hashes w3c/webappsec-subresource-integrity#118, by @jb-wisemo.
-
-
2 issues closed.
-
Check all hashes w3c/webappsec-subresource-integrity#118.
-
Reference the IANA registry of hash names w3c/webappsec-subresource-integrity#119.
-
-
3 issues received 9 new comments.
-
Reference the IANA registry of hash names w3c/webappsec-subresource-integrity#119 (6 comments by @annevk, @awwright, @jb-wisemo, @mozfreddyb)
-
-
1 pull request merged.
-
Edit 3.3.2 Parse metadata in more detail w3c/webappsec-subresource-integrity#110.
-
-
1 pull request received 15 new comments.
-
Edit 3.3.2 Parse metadata in more detail w3c/webappsec-subresource-integrity#110 (15 comments by @annevk, @baek9, @domfarolino, @sideshowbarker)
-
w3c/webappsec-csp
-
3 issues opened.
-
Should we replace browsing contexts with navigables? w3c/webappsec-csp#579, by @antosart.
-
Directive's value is a set w3c/webappsec-csp#577, by @annevk.
-
Broken references in Content Security Policy Level 3 w3c/webappsec-csp#576, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Non-ASCII characters in CSP policy. w3c/webappsec-csp#473.
-
-
8 issues received 12 new comments.
-
Clarify/test which quote characters may be used w3c/webappsec-csp#434 (4 comments by @annevk, @antosart, @evilpie)
-
Should we replace browsing contexts with navigables? w3c/webappsec-csp#579 (2 comments by @antosart, @domenic)
-
Introduce rate limiting for violation reports (report-uri and report-to) w3c/webappsec-csp#227 (1 comment by @odinho)
-
Add way to define all country code top-level domain. w3c/webappsec-csp#256 (1 comment by @MykolaiKorniat)
-
Enable CSP3 `'unsafe-hashes'` for script `src` attributes w3c/webappsec-csp#574 (1 comment by @letitz)
-
The editor's draft includes several features that no one has shipped. w3c/webappsec-csp#563 (1 comment by @eligrey)
-
-
2 pull requests opened.
-
Fix references to html after navigation and session history rewrite w3c/webappsec-csp#580, by @antosart.
-
Fix for each iterations referring to infra w3c/webappsec-csp#578, by @antosart.
-
-
2 pull requests received 15 new comments.
-
Fix references to html after navigation and session history rewrite w3c/webappsec-csp#580 (12 comments by @annevk, @antosart, @mikewest)
-
w3c/webappsec-mixed-content
-
1 issue received 1 new comment.
-
Clarify mixed content behavior for access to origins in CIDR 127.0.0.0/8 or ::1/128 w3c/webappsec-mixed-content#17 (1 comment by @paulsemel)
-
w3c/webcrypto
-
4 issues opened.
-
Persistent storage of key w3c/webcrypto#331, by @nikosft.
-
problems importing PEM from Httb Bis WGs Signatures 13 draft w3c/webcrypto#330, by @bblfish.
-
Consider making the deriveBits length argument optional w3c/webcrypto#329, by @twiss.
-
Adopt a PR template of sorts w3c/webcrypto#327, by @annevk.
-
-
2 issues closed.
-
Adopt a PR template of sorts w3c/webcrypto#327.
-
RSA encryption not allowed with Private Key? w3c/webcrypto#315.
-
-
6 issues received 23 new comments.
-
Consider making the deriveBits length argument optional w3c/webcrypto#329 (10 comments by @annevk, @panva, @twiss)
-
deriveBits length idl does not allow null w3c/webcrypto#322 (9 comments by @annevk, @panva, @saschanaz, @twiss)
-
problems importing PEM from Httb Bis WGs Signatures 13 draft w3c/webcrypto#330 (1 comment by @panva)
-
-
1 pull request opened.
-
Add GitHub Pull Request Template w3c/webcrypto#328, by @twiss.
-
-
1 pull request merged.
-
Add GitHub Pull Request Template w3c/webcrypto#328.
-
-
1 pull request received 3 new comments.
w3c/webappsec-upgrade-insecure-requests
-
1 issue opened.
-
Specify value of Origin header (CORS) after a scheme upgrade w3c/webappsec-upgrade-insecure-requests#32, by @Rob--W.
-
-
1 issue closed.
-
Specify value of Origin header (CORS) after a scheme upgrade w3c/webappsec-upgrade-insecure-requests#32.
-
-
1 issue received 2 new comments.
-
Specify value of Origin header (CORS) after a scheme upgrade w3c/webappsec-upgrade-insecure-requests#32 (2 comments by @annevk, @Rob--W)
-
w3c/webappsec-referrer-policy
-
1 issue received 2 new comments.
-
Add referrerpolicy to media elements (<audio> and <video>) w3c/webappsec-referrer-policy#160 (2 comments by @annevk, @chrisgraham)
-
-
1 pull request received 2 new comments.
-
Omit referrers on cross-origin requests from an .onion address w3c/webappsec-referrer-policy#156 (2 comments by @domfarolino, @fmarier)
-
w3c/webappsec-cspee
-
1 issue opened.
-
Broken references in Content Security Policy: Embedded Enforcement w3c/webappsec-cspee#27, by @dontcallmedom-bot.
-
-
2 issues received 6 new comments.
-
Status of CSPEE spec? Implementor interest? w3c/webappsec-cspee#19 (4 comments by @annevk, @RuslanZavacky)
-
Buggy behavior with multiple nested frames w3c/webappsec-cspee#26 (2 comments by @arturjanc, @camillelamy)
-
w3c/webappsec-credential-management
-
1 issue opened.
-
Pass global object to DiscoverFromExternalSource w3c/webappsec-credential-management#210, by @npm1.
-
w3c/permissions-registry
-
1 issue received 1 new comment.
-
Update "change process" now that <dfn permission> is a thing w3c/permissions-registry#17 (1 comment by @miketaylr)
-
-
1 pull request opened.
-
Add `window-management` to table of provisional permissions. w3c/permissions-registry#19, by @bradtriebwasser.
-
-
1 pull request merged.
-
Add `window-management` to table of provisional permissions. w3c/permissions-registry#19.
-
-
1 pull request received 4 new comments.
-
Add `window-management` to table of provisional permissions. w3c/permissions-registry#19 (4 comments by @bradtriebwasser, @miketaylr)
-
TR publications
-
5 documents published.
-
Permissions published as a Working Draft. History of Permissions
-
Content Security Policy Level 3 published 4 times as a Working Draft. History of Content Security Policy Level 3
-
Past meetings
-
1 meeting.
GitHub
w3c/permissions-registry
-
2 issues opened.
-
What to do with experimental features? w3c/permissions-registry#18, by @miketaylr.
-
Update "change process" now that <dfn permission> is a thing w3c/permissions-registry#17, by @miketaylr.
-
-
1 issue received 3 new comments.
-
Update "change process" now that <dfn permission> is a thing w3c/permissions-registry#17 (3 comments by @miketaylr)
-
-
3 pull requests opened.
-
Add "accelerometer" to registry w3c/permissions-registry#16, by @miketaylr.
-
Add "push" to registry w3c/permissions-registry#15, by @miketaylr.
-
Add "notifications" to registry w3c/permissions-registry#14, by @miketaylr.
-
-
3 pull requests merged.
-
Add "accelerometer" to registry w3c/permissions-registry#16.
-
Add "push" to registry w3c/permissions-registry#15.
-
Add "notifications" to registry w3c/permissions-registry#14.
-
-
3 pull requests received 8 new comments.
-
Add "accelerometer" to registry w3c/permissions-registry#16 (3 comments by @marcoscaceres, @miketaylr)
-
Add "notifications" to registry w3c/permissions-registry#14 (2 comments by @marcoscaceres, @miketaylr)
-
w3c/webcrypto
-
1 issue opened.
-
deriveBits length idl does not allow null w3c/webcrypto#322, by @panva.
-
-
1 issue closed.
-
Calling key wrap operation on a JWK encoding w3c/webcrypto#187.
-
-
2 issues received 24 new comments.
-
deriveBits length idl does not allow null w3c/webcrypto#322 (22 comments by @martinthomson, @panva, @saschanaz, @twiss)
-
-
5 pull requests opened.
-
Remove reference to DSA OID w3c/webcrypto#326, by @twiss.
-
Remove support for importing RSA and ECC keys with alternative OIDs w3c/webcrypto#325, by @twiss.
-
Make length parameter nullable in deriveBits WebIDL w3c/webcrypto#324, by @twiss.
-
fix: make deriveBits length webidl nullable w3c/webcrypto#323, by @panva.
-
nit: Derive Bits w3c/webcrypto#321, by @panva.
-
-
1 pull request merged.
-
nit: Derive Bits w3c/webcrypto#321.
-
-
2 pull requests closed.
-
fix: make deriveBits length webidl nullable w3c/webcrypto#323.
-
Mark CryptoKeyPair fields as required w3c/webcrypto#291.
-
-
4 pull requests received 6 new comments.
-
Remove support for importing RSA and ECC keys with alternative OIDs w3c/webcrypto#325 (1 comment by @panva)
w3c/webappsec-clear-site-data
-
1 issue received 3 new comments.
w3c/permissions
-
4 issues opened.
-
Allow returning "prompt" rather than "denied" w3c/permissions#388, by @annevk.
-
Potentially revisit oneRealm w3c/permissions#387, by @annevk.
-
Set Permission vagueness w3c/permissions#386, by @annevk.
-
Can we more formally define the "Permission Store" w3c/permissions#384, by @annevk.
-
-
5 issues received 12 new comments.
-
Can we more formally define the "Permission Store" w3c/permissions#384 (6 comments by @annevk, @johannhof, @jyasskin, @marcoscaceres, @miketaylr)
-
Potentially revisit oneRealm w3c/permissions#387 (3 comments by @johannhof, @marcoscaceres, @miketaylr)
-
-
1 pull request opened.
-
Meta: remove local-lt for <dfn>permission state<dfn> w3c/permissions#385, by @miketaylr.
-
-
1 pull request merged.
-
Meta: remove local-lt for <dfn>permission state<dfn> w3c/permissions#385.
-
w3c/webappsec-cspee
-
1 issue received 2 new comments.
-
Buggy behavior with multiple nested frames w3c/webappsec-cspee#26 (2 comments by @camillelamy, @qabandi)
-
w3c/webappsec-csp
-
5 issues opened.
-
`'report-hash'`: Adding hashes of blocked content to violation reports w3c/webappsec-csp#575, by @arturjanc.
-
Enable CSP3 `'unsafe-hashes'` for script `src` attributes w3c/webappsec-csp#574, by @arturjanc.
-
CSS and JSON module scripts w3c/webappsec-csp#573, by @annevk.
-
Broken references in Content Security Policy Level 3 w3c/webappsec-csp#571, by @dontcallmedom-bot.
-
How to block javascript injection in app webview. w3c/webappsec-csp#570, by @lufengd3.
-
-
5 issues closed.
-
Link to updated reporting interface w3c/webappsec-csp#565.
-
Broken references in Content Security Policy Level 3 w3c/webappsec-csp#571.
-
How to block javascript injection in app webview. w3c/webappsec-csp#570.
-
Should Workers inherit CSP directives from the parent context? w3c/webappsec-csp#336.
-
“Report a violation” can seemingly reach “fire an event at” w/ WorkletGlobalScope w3c/webappsec-csp#545.
-
-
8 issues received 24 new comments.
-
Should Workers inherit CSP directives from the parent context? w3c/webappsec-csp#336 (7 comments by @annevk, @antosart, @codehag, @smaug----)
-
`'report-hash'`: Adding hashes of blocked content to violation reports w3c/webappsec-csp#575 (5 comments by @arturjanc, @letitz, @mikewest)
-
How to block javascript injection in app webview. w3c/webappsec-csp#570 (4 comments by @dveditz, @jonathanKingston, @lufengd3)
-
Enable CSP3 `'unsafe-hashes'` for script `src` attributes w3c/webappsec-csp#574 (3 comments by @arturjanc, @letitz, @mikewest)
-
The editor's draft includes several features that no one has shipped. w3c/webappsec-csp#563 (2 comments by @annevk, @dveditz)
-
parser_inserted flag used in 'strict-dynamic' check is not sufficient w3c/webappsec-csp#376 (1 comment by @shhnjk)
-
“Report a violation” can seemingly reach “fire an event at” w/ WorkletGlobalScope w3c/webappsec-csp#545 (1 comment by @antosart)
-
Make user's the driver of the user-agent again: bookmarklets, userscripts w3c/webappsec-csp#444 (1 comment by @rektide)
-
-
3 pull requests opened.
-
Fix references to other specs w3c/webappsec-csp#572, by @antosart.
-
Fix validation of CSS markup w3c/webappsec-csp#569, by @antosart.
-
Define securitypolicyviolation event w3c/webappsec-csp#568, by @tidoust.
-
-
5 pull requests merged.
-
Fix link to updated reporting interface w3c/webappsec-csp#566.
-
Fix references to other specs w3c/webappsec-csp#572.
-
Add support for the webidentity destination w3c/webappsec-csp#567.
-
Define securitypolicyviolation event w3c/webappsec-csp#568.
-
Fix validation of CSS markup w3c/webappsec-csp#569.
-
-
6 pull requests received 20 new comments.
-
Define securitypolicyviolation event w3c/webappsec-csp#568 (6 comments by @antosart, @dontcallmedom, @tidoust)
-
Add support for the webidentity destination w3c/webappsec-csp#567 (3 comments by @antosart, @cbiesinger, @clelland)
-
w3c/trusted-types
-
2 pull requests opened.
-
Add detail about fromLiteral to explainer. w3c/trusted-types#377, by @otherdaniel.
-
Explain fromLiteral methods. w3c/trusted-types#376, by @otherdaniel.
-
-
2 pull requests merged.
-
Explain fromLiteral methods. w3c/trusted-types#376.
-
Modify the script slot setting algorithms. w3c/trusted-types#372.
-
w3c/webappsec
-
1 issue opened.
-
Different behavior with CSP and HTML imports w3c/webappsec#616, by @lmuntaner.
-
-
1 issue received 1 new comment.
w3c/webappsec-upgrade-insecure-requests
-
1 pull request opened.
-
Fix "environment settings object" URL w3c/webappsec-upgrade-insecure-requests#31, by @Ms2ger.
-
-
1 pull request merged.
-
Fix "environment settings object" URL w3c/webappsec-upgrade-insecure-requests#31.
-
-
1 pull request received 2 new comments.
-
Fix "environment settings object" URL w3c/webappsec-upgrade-insecure-requests#31 (2 comments by @annevk, @w3cbot)
-
w3c/webappsec-permissions-policy
-
1 issue received 1 new comment.
-
Usefulness of reporting in Permissions Policy w3c/webappsec-permissions-policy#386 (1 comment by @csharrison)
-
-
1 pull request received 10 new comments.
-
Wildcards in Permissions Policy Origins w3c/webappsec-permissions-policy#482 (10 comments by @annevk, @arichiv)
-
TR publications
-
4 documents published.
-
Content Security Policy Level 3 published as a Working Draft. History of Content Security Policy Level 3
-
Permissions published as a Working Draft. History of Permissions
-
A Well-Known URL for Changing Passwords published as a First Public Working Draft. History of A Well-Known URL for Changing Passwords
-
Trusted Types published as a First Public Working Draft. History of Trusted Types
-
Past meetings
Participants
-
12 participants joined.
-
Austin Cain (Shopify) joined.
-
John Harney (Defense Information Systems Agency) joined.
-
Andrey Zaytsev (Google LLC) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
Eryn Wells (Apple Inc.) joined.
-
Ricky Mondello (Apple Inc.) joined.
-
John Wilander (Apple Inc.) joined.
-
Samuel Weinig (Apple Inc.) joined.
-
Alexey Proskuryakov (Apple Inc.) joined.
-
Theresa O'Connor (Apple Inc.) joined.
-
Anne van Kesteren (Apple Inc.) joined.
-
世奇 李 (ByteDance) joined.
-
-
3 organizations joined.
-
Shopify joined.
-
Defense Information Systems Agency joined.
-
Apple Inc. joined.
-
GitHub
w3c/webappsec-csp
-
2 issues opened.
-
Link to updated reporting interface w3c/webappsec-csp#565, by @jyasskin.
-
The editor's draft includes several features that no one has shipped. w3c/webappsec-csp#563, by @mikewest.
-
-
1 issue closed.
-
"Get the effective directive for request" should handle at least worklets w3c/webappsec-csp#554.
-
-
1 issue reopened.
-
問題追縱 w3c/webappsec-csp#562, by @viv718918.
-
-
3 issues received 12 new comments.
-
The editor's draft includes several features that no one has shipped. w3c/webappsec-csp#563 (9 comments by @annevk, @domenic, @mikewest, @noamr, @yoavweiss)
-
-
3 pull requests opened.
-
Add support for the webidentity destination w3c/webappsec-csp#567, by @cbiesinger.
-
Fix link to updated reporting interface w3c/webappsec-csp#566, by @antosart.
-
Remove `navigate-to`. w3c/webappsec-csp#564, by @mikewest.
-
-
3 pull requests merged.
-
Remove `navigate-to`. w3c/webappsec-csp#564.
-
Return correct effective directive for worklets w3c/webappsec-csp#555.
-
Editorial: Clarify the role of `'none'` in source lists. w3c/webappsec-csp#534.
-
-
3 pull requests received 4 new comments.
w3c/webappsec-permissions-policy
-
2 issues opened.
-
"Process permissions policy attributes" unclear w3c/webappsec-permissions-policy#489, by @annevk.
-
Set up auto-publishing w3c/webappsec-permissions-policy#487, by @clelland.
-
-
6 issues received 16 new comments.
-
Proposal: allow grouping permissions by year w3c/webappsec-permissions-policy#481 (8 comments by @annevk, @bershanskiy, @ecki, @Seirdy)
-
Usefulness of reporting in Permissions Policy w3c/webappsec-permissions-policy#386 (2 comments by @annevk, @bartoszniemczura)
-
Denying self while still allowing subframes w3c/webappsec-permissions-policy#480 (2 comments by @annevk, @clelland)
-
How do I disable everything? w3c/webappsec-permissions-policy#208 (2 comments by @AramZS, @samuelweiler)
-
Deny all like alias for the Permission-Policy: Header w3c/webappsec-permissions-policy#483 (1 comment by @ecki)
-
-
4 pull requests opened.
-
Propose identity-credential-get permission policy w3c/webappsec-permissions-policy#488, by @pkotwicz2.
-
Use spec-prod instead of Travis CI. w3c/webappsec-permissions-policy#486, by @jyasskin.
-
Turn on PR Preview w3c/webappsec-permissions-policy#485, by @jyasskin.
-
Reference "generate and queue a report" w3c/webappsec-permissions-policy#484, by @clelland.
-
-
3 pull requests merged.
-
Use spec-prod instead of Travis CI. w3c/webappsec-permissions-policy#486.
-
Turn on PR Preview w3c/webappsec-permissions-policy#485.
-
Editorial: export * and 'self' w3c/webappsec-permissions-policy#474.
-
-
3 pull requests received 11 new comments.
-
Wildcards in Permissions Policy Origins w3c/webappsec-permissions-policy#482 (6 comments by @arichiv, @clelland)
-
Use spec-prod instead of Travis CI. w3c/webappsec-permissions-policy#486 (4 comments by @clelland, @jyasskin, @marcoscaceres, @sideshowbarker)
-
w3c/webappsec-cspee
-
1 issue received 1 new comment.
w3c/webappsec-credential-management
-
1 issue closed.
-
Specify what happens when a credential request is issued while another one is in progress w3c/webappsec-credential-management#206.
-
-
2 pull requests opened.
-
Add support for publickey-credentials-create permission policy w3c/webappsec-credential-management#209, by @stephenmcgruer.
-
Remove custom anchors for FedCM w3c/webappsec-credential-management#208, by @johannhof.
-
-
2 pull requests merged.
-
Disallow multiple in-progress credential requests w3c/webappsec-credential-management#207.
-
Remove custom anchors for FedCM w3c/webappsec-credential-management#208.
-
-
3 pull requests received 12 new comments.
-
Disallow multiple in-progress credential requests w3c/webappsec-credential-management#207 (8 comments by @npm1, @nsatragno)
-
Add support for publickey-credentials-create permission policy w3c/webappsec-credential-management#209 (3 comments by @johannhof, @stephenmcgruer)
-
Add permissions policy check for FedCM w3c/webappsec-credential-management#204 (1 comment by @tabatkins)
-
w3c/trusted-types
-
1 issue opened.
-
TrustedHTML.fromLiteral is exposed in workers but assumes the current global is a Window w3c/trusted-types#374, by @Ms2ger.
-
-
1 issue closed.
-
Figure out if there is a better way to guard navigations to `javascript:` across documents w3c/trusted-types#363.
-
-
1 issue received 1 new comment.
-
Figure out if there is a better way to guard navigations to `javascript:` across documents w3c/trusted-types#363 (1 comment by @shhnjk)
-
-
1 pull request opened.
-
Changed the links to reflect the renamed repository. w3c/trusted-types#375, by @koto.
-
-
1 pull request merged.
-
Changed the links to reflect the renamed repository. w3c/trusted-types#375.
-
w3c/webappsec-upgrade-insecure-requests
-
3 pull requests opened.
-
Fix PR Preview w3c/webappsec-upgrade-insecure-requests#30, by @jyasskin.
-
Flag PRs if they add warnings to the Bikeshed build w3c/webappsec-upgrade-insecure-requests#29, by @jyasskin.
-
Replace Mike with Carlos as the editor w3c/webappsec-upgrade-insecure-requests#28, by @jyasskin.
-
-
3 pull requests merged.
-
Replace Mike with Carlos as the editor w3c/webappsec-upgrade-insecure-requests#28.
-
Fix PR Preview w3c/webappsec-upgrade-insecure-requests#30.
-
Flag PRs if they add warnings to the Bikeshed build w3c/webappsec-upgrade-insecure-requests#29.
-
-
1 pull request received 1 new comment.
-
Replace Mike with Carlos as the editor w3c/webappsec-upgrade-insecure-requests#28 (1 comment by @mikewest)
-
w3c/permissions-registry
-
2 issues received 3 new comments.
-
CFC for publication as a "Draft Registry" w3c/permissions-registry#4 (2 comments by @annevk, @miketaylr)
-
Removal of PermissionName broke downstream standards w3c/permissions-registry#11 (1 comment by @rakuco)
-
w3c/webappsec
-
1 pull request opened.
-
Adding my name to attendees list w3c/webappsec#615, by @seanturner.
-
-
1 pull request merged.
-
Adding my name to attendees list w3c/webappsec#615.
-
w3c/webappsec-subresource-integrity
-
1 issue received 1 new comment.
-
Consider integrity enforcement of iframe w3c/webappsec-subresource-integrity#21 (1 comment by @nathanfranke)
-
w3c/permissions
-
1 issue opened.
-
Can we extend the manifest file so that extensions can extend the permissions API? w3c/permissions#383, by @kdenhartog.
-
-
1 issue closed.
-
Can we extend the manifest file so that extensions can extend the permissions API? w3c/permissions#383.
-
-
1 issue received 3 new comments.
-
Can we extend the manifest file so that extensions can extend the permissions API? w3c/permissions#383 (3 comments by @jyasskin, @kdenhartog, @KOLANICH)
-
w3c/webcrypto
-
1 issue closed.
-
Set limits on saltLength w3c/webcrypto#318.
-
-
1 issue received 1 new comment.
Past meetings
-
1 meeting.
GitHub
w3c/webappsec-credential-management
-
1 issue opened.
-
Specify what happens when a credential request is issued while another one is in progress w3c/webappsec-credential-management#206, by @nsatragno.
-
-
2 pull requests opened.
-
Disallow multiple in-progress credential requests w3c/webappsec-credential-management#207, by @npm1.
-
Add permissions policy check for FedCM w3c/webappsec-credential-management#204, by @johannhof.
-
-
1 pull request merged.
-
Add permissions policy check for FedCM w3c/webappsec-credential-management#204.
-
-
3 pull requests received 18 new comments.
-
Add permissions policy check for FedCM w3c/webappsec-credential-management#204 (11 comments by @johannhof, @npm1, @nsatragno)
-
Disallow multiple in-progress credential requests w3c/webappsec-credential-management#207 (6 comments by @johannhof, @npm1, @nsatragno)
-
Correctly indent "Terminate these substeps" (fixes #202) w3c/webappsec-credential-management#203 (1 comment by @johannhof)
-
w3c/webappsec-permissions-policy
-
2 issues opened.
-
Deny all like alias for the Permission-Policy: Header w3c/webappsec-permissions-policy#483, by @ecki.
-
Proposal: allow grouping permissions by year w3c/webappsec-permissions-policy#481, by @Seirdy.
-
-
3 issues received 3 new comments.
-
Deny all like alias for the Permission-Policy: Header w3c/webappsec-permissions-policy#483 (1 comment by @ecki)
-
Proposal: allow grouping permissions by year w3c/webappsec-permissions-policy#481 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Wildcards in Permissions Policy Origins w3c/webappsec-permissions-policy#482, by @arichiv.
-
-
1 pull request merged.
-
reserve "unload" permissions policy name w3c/webappsec-permissions-policy#477.
-
-
1 pull request received 16 new comments.
-
Wildcards in Permissions Policy Origins w3c/webappsec-permissions-policy#482 (16 comments by @arichiv, @clelland, @yoavweiss)
-
w3c/webappsec-cspee
-
1 issue opened.
-
Buggy behavior with multiple nested frames w3c/webappsec-cspee#26, by @antosart.
-
-
1 issue received 3 new comments.
-
Buggy behavior with multiple nested frames w3c/webappsec-cspee#26 (3 comments by @antosart, @qabandi)
-
w3c/webappsec-csp
-
1 issue opened.
-
Add WPT tests that test base64url characters for hashes and nonces w3c/webappsec-csp#560, by @dveditz.
-
-
2 issues closed.
-
Add WPT tests that test base64url characters for hashes and nonces w3c/webappsec-csp#560.
-
[csp-embedded-enforcement] Buggy behavior with multiple nested frames w3c/webappsec-csp#558.
-
-
4 issues received 10 new comments.
-
Add WPT tests that test base64url characters for hashes and nonces w3c/webappsec-csp#560 (2 comments by @mozfreddyb)
-
Prevent CSP reports being sent if I handle the SecurityPolicyViolation event. w3c/webappsec-csp#255 (2 comments by @Elisheva-Jacobson, @michaelficarra)
-
[csp-embedded-enforcement] Buggy behavior with multiple nested frames w3c/webappsec-csp#558 (1 comment by @antosart)
-
1 pull request opened.
-
Update X-Frame-Options discussion w3c/webappsec-csp#559, by @domenic.
-
-
1 pull request merged.
-
Update X-Frame-Options discussion w3c/webappsec-csp#559.
-
w3c/webappsec-subresource-integrity
-
1 issue received 7 new comments.
-
Consider integrity check violation reporting w3c/webappsec-subresource-integrity#20 (7 comments by @annevk, @devd, @mozfreddyb, @ScottHelme)
-
w3c/webappsec
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update 2022-08-17-minutes.md w3c/webappsec#614, by @twiss.
-
-
1 pull request merged.
-
Update 2022-08-17-minutes.md w3c/webappsec#614.
-
w3c/webappsec-clear-site-data
-
1 issue closed.
-
typo on index.html w3c/webappsec-clear-site-data#57.
-
w3c/trusted-types
-
1 issue opened.
-
Polyfill script link on w3c.github.io gives 404 w3c/trusted-types#373, by @siMs0n.
-
-
1 issue closed.
-
Polyfill script link on w3c.github.io gives 404 w3c/trusted-types#373.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Modify the script slot setting algorithms. w3c/trusted-types#372, by @koto.
-
w3c/webcrypto
-
2 issues received 3 new comments.
TR publications
-
1 document published.
-
Permissions published as a Working Draft. History of Permissions
-
Participants
-
1 Team contact stepped down.
-
Michael[tm] Smith (sideshowbarker) stepped down as a Team contact.
-
-
2 participants joined.
-
Mingzhe Li (Akamai Technologies) joined.
-
Jun Kokatsu (Google LLC) joined.
-
-
27 participants left.
-
Tanvi Vyas (Mozilla Foundation) left.
-
lawil karama (Snake Nation) left.
-
Julien Rossi (CANTON CONSULTING) left.
-
Orie Steele (Transmute) left.
-
Marcos Caceres (Apple Inc.) left.
-
S Tran (Wikimedia Foundation) left.
-
Josh Carlson (Brightcove) left.
-
Eryn Wells (Apple Inc.) left.
-
Mingzhe Li (Akamai Technologies) left.
-
Mingqiu Sun (Intel Corporation) left.
-
Martin Meyer (Akamai Technologies) left.
-
Ricky Mondello (Apple Inc.) left.
-
Eiji Yamamoto (Mitsubishi Electric Corporation) left.
-
jianfang ru (Alibaba Group) left.
-
Michael Specter (W3C Invited Experts) left.
-
Michael Pennisi (Bocoup) left.
-
Daniel Abeles (Akamai Technologies) left.
-
Jianjun Zhu (Intel Corporation) left.
-
Abdulrahman Alkhelaifi (W3C Invited Experts) left.
-
Michael Tiffany (HUMAN) left.
-
Malika Aubakirova (W3C Invited Experts) left.
-
Niklas Andreasson (W3C Invited Experts) left.
-
John Wilander (Apple Inc.) left.
-
Samuel Weinig (Apple Inc.) left.
-
Jonathan Kingston (Duck Duck Go, Inc.) left.
-
Theresa O'Connor (Apple Inc.) left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
-
4 organizations joined.
-
Akamai Technologies joined.
-
Entersekt joined.
-
Digital Bazaar joined.
-
Meta joined.
-
-
1 organization left.
-
Digital Bazaar left.
-
GitHub
w3c/webcrypto
-
5 issues opened.
-
SHA-3 (Keccak) support w3c/webcrypto#319, by @Neustradamus.
-
Set limits on saltLength w3c/webcrypto#318, by @angelaizg.
-
ECDSA adding curve brainpoolP384 w3c/webcrypto#317, by @Sunshineguru.
-
Add support for SM3 w3c/webcrypto#316, by @zzl360.
-
RSA encryption not allowed with Private Key? w3c/webcrypto#315, by @markcellus.
-
-
5 issues received 25 new comments.
-
Please require a secure origin (Bug 25972) w3c/webcrypto#28 (14 comments by @ghost, @robofearth, @twiss, @X-Ryl669)
-
RSA encryption not allowed with Private Key? w3c/webcrypto#315 (5 comments by @markcellus, @tniessen)
-
w3c/permissions
-
1 issue closed.
-
Add an introduction section? w3c/permissions#274.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Editorial: add an introduction w3c/permissions#381, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: add an introduction w3c/permissions#381.
-
-
2 pull requests received 11 new comments.
-
w3c/permissions#382 (1 comment by @w3cbot)
w3c/webappsec-csp
-
4 issues opened.
-
[csp-embedded-enforcement] Buggy behavior with multiple nested frames w3c/webappsec-csp#558, by @qabandi.
-
Correct the link for CSP3 in the CSP2 Page w3c/webappsec-csp#556, by @Abdulali97.
-
"Get the effective directive for request" should handle at least worklets w3c/webappsec-csp#554, by @evilpie.
-
Regarding hashes for JS URL w3c/webappsec-csp#553, by @seongil-wi.
-
-
3 issues received 4 new comments.
-
"Get the effective directive for request" should handle at least worklets w3c/webappsec-csp#554 (2 comments by @antosart, @evilpie)
-
Make user's the driver of the user-agent again: bookmarklets, userscripts w3c/webappsec-csp#444 (1 comment by @rektide)
-
Prevent CSP reports being sent if I handle the SecurityPolicyViolation event. w3c/webappsec-csp#255 (1 comment by @Elisheva-Jacobson)
-
-
3 pull requests opened.
-
Update broken Wasm links w3c/webappsec-csp#557, by @dotproto.
-
Return correct effective directive for worklets w3c/webappsec-csp#555, by @antosart.
-
Link to HTML spec definition of securitypolicyviolation event w3c/webappsec-csp#552, by @dontcallmedom.
-
-
1 pull request merged.
-
Link to HTML spec definition of securitypolicyviolation event w3c/webappsec-csp#552.
-
w3c/webappsec-credential-management
-
1 issue opened.
-
"Terminate these substeps" seems to have wrong indentation w3c/webappsec-credential-management#202, by @johannhof.
-
-
1 issue closed.
-
"Terminate these substeps" seems to have wrong indentation w3c/webappsec-credential-management#202.
-
-
2 pull requests opened.
-
Correctly indent "Terminate these substeps" (fixes #202) w3c/webappsec-credential-management#203, by @johannhof.
-
Add IdentityCredential to Credential Type Registry w3c/webappsec-credential-management#201, by @npm1.
-
-
2 pull requests merged.
-
Add IdentityCredential to Credential Type Registry w3c/webappsec-credential-management#201.
-
Correctly indent "Terminate these substeps" (fixes #202) w3c/webappsec-credential-management#203.
-
-
1 pull request received 7 new comments.
-
Add IdentityCredential to Credential Type Registry w3c/webappsec-credential-management#201 (7 comments by @johannhof, @npm1)
-
w3c/webappsec-permissions-policy
-
3 issues opened.
-
Denying self while still allowing subframes w3c/webappsec-permissions-policy#480, by @fergald.
-
Client Hint delegation to multiple subdomains w3c/webappsec-permissions-policy#479, by @nicjansma.
-
Mark "ambient-light-sensor" as behind a flag in features.md w3c/webappsec-permissions-policy#478, by @o3-steven.
-
-
1 issue reopened.
-
Mark "ambient-light-sensor" as behind a flag in features.md w3c/webappsec-permissions-policy#478, by @miketaylr.
-
-
2 issues received 13 new comments.
-
Client Hint delegation to multiple subdomains w3c/webappsec-permissions-policy#479 (10 comments by @arichiv, @clelland, @miketaylr, @mikewest, @yoavweiss)
-
Mark "ambient-light-sensor" as behind a flag in features.md w3c/webappsec-permissions-policy#478 (3 comments by @miketaylr, @o3-steven)
-
-
1 pull request opened.
-
reserve "unload" permissions policy name w3c/webappsec-permissions-policy#477, by @fergald.
-
w3c/permissions-registry
-
1 issue received 2 new comments.
-
CFC for publication as a "Draft Registry" w3c/permissions-registry#4 (2 comments by @marcoscaceres, @miketaylr)
-
w3c/trusted-types
-
1 pull request opened.
-
docs: Include repository field in package.json w3c/trusted-types#371, by @eps1lon.
-
w3c/webappsec-secure-contexts
-
1 issue received 1 new comment.
-
Using secure-context gated features with local devices w3c/webappsec-secure-contexts#60 (1 comment by @vincentlaucsb)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 July 2023. Participants had to rejoin under this charter.
-
Past meetings
-
1 meeting.
Participants
-
4 participants joined.
-
Maitane Zotes (Cloudflare) joined.
-
Philipp Pfeiffenberger (Google LLC) joined.
-
Daniel Huigens (Proton AG) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
-
2 participants left.
-
Pranjal Jumde (Brave Software Inc.) left.
-
Daniel Bates (Apple Inc.) left.
-
-
12 organizations joined.
-
MITRE Corporation joined.
-
Cloudflare joined.
-
Brave Software Inc. joined.
-
Adobe joined.
-
Digital Bazaar joined.
-
HM Government joined.
-
RingCentral joined.
-
ByteDance joined.
-
Google LLC joined.
-
Mozilla Foundation joined.
-
Microsoft Corporation joined.
-
Proton AG joined.
-
-
29 organizations left.
-
Snake Nation left.
-
CANTON CONSULTING left.
-
Transmute left.
-
ByteDance left.
-
Wikimedia Foundation left.
-
Duck Duck Go, Inc. left.
-
Brightcove left.
-
Igalia left.
-
The Washington Post left.
-
RingCentral left.
-
Entersekt left.
-
Saudi Federation for Cybersecurity, Programming, and Drones left.
-
Mitsubishi Electric Corporation left.
-
Alibaba Group left.
-
Brave Software Inc. left.
-
Bocoup left.
-
Akamai Technologies left.
-
HM Government left.
-
Microsoft Corporation left.
-
Apple Inc. left.
-
HUMAN left.
-
Digital Bazaar left.
-
MITRE Corporation left.
-
Adobe left.
-
Meta left.
-
Intel Corporation left.
-
Mozilla Foundation left.
-
Google LLC left.
-
OpenJS Foundation left.
-
GitHub
w3c/webappsec-csp
-
2 issues opened.
-
when using report-uri / report-to when in report only mode `blocked-uri` is returned as `inline` w3c/webappsec-csp#551, by @allen-munsch.
-
Problem caused by script-src-elem 'nonce-<nonce>' 'strcit-dynamic' w3c/webappsec-csp#548, by @seongil-wi.
-
-
3 issues received 4 new comments.
-
when using report-uri / report-to when in report only mode `blocked-uri` is returned as `inline` w3c/webappsec-csp#551 (2 comments by @allen-munsch, @antosart)
-
Problem caused by script-src-elem 'nonce-<nonce>' 'strcit-dynamic' w3c/webappsec-csp#548 (1 comment by @antosart)
-
-
2 pull requests opened.
-
Check for an EventTarget before dispatching violation events w3c/webappsec-csp#549, by @antosart.
-
2 pull requests merged.
-
Check for an EventTarget before dispatching violation events w3c/webappsec-csp#549.
-
Fix build w3c/webappsec-csp#550.
-
-
1 pull request received 2 new comments.
-
Check for an EventTarget before dispatching violation events w3c/webappsec-csp#549 (2 comments by @antosart, @domenic)
-
w3c/webappsec-credential-management
-
1 issue opened.
-
Make isConditionalMediationAvailable() return a promise w3c/webappsec-credential-management#199, by @nsatragno.
-
-
1 issue closed.
-
Make isConditionalMediationAvailable() return a promise w3c/webappsec-credential-management#199.
-
-
1 pull request opened.
-
isConditionalMediationAvailable() returns promise w3c/webappsec-credential-management#200, by @nsatragno.
-
-
1 pull request merged.
-
isConditionalMediationAvailable() returns promise w3c/webappsec-credential-management#200.
-
-
1 pull request received 3 new comments.
-
isConditionalMediationAvailable() returns promise w3c/webappsec-credential-management#200 (3 comments by @npm1, @nsatragno)
-
w3c/webappsec-subresource-integrity
-
1 issue received 12 new comments.
-
Consider integrity check violation reporting w3c/webappsec-subresource-integrity#20 (12 comments by @devd, @jonathanKingston, @mikewest, @mozfreddyb, @ScottHelme)
-
w3c/webcrypto
-
2 issues closed.
-
support for Curve25519 in WebCrypto. w3c/webcrypto#233.
-
How to best propose features and show implementor interest w3c/webcrypto#280.
-
-
8 issues received 9 new comments.
-
Bug 27755 - Using the Subtle Crypto Interface with Streams w3c/webcrypto#73 (1 comment by @simonhaenisch)
-
PROPOSAL: Add support for general (hardware backed) cryptographic signatures and key exchange w3c/webcrypto#263 (1 comment by @twiss)
w3c/webappsec-permissions-policy
-
1 issue opened.
-
A "no-op" policy to support feature-agnostic testing w3c/webappsec-permissions-policy#475, by @mustaqahmed.
-
-
1 issue closed.
-
New permission policy features that should get a mention in this repo w3c/webappsec-permissions-policy#471.
-
-
1 issue received 2 new comments.
-
A "no-op" policy to support feature-agnostic testing w3c/webappsec-permissions-policy#475 (2 comments by @flackr, @mustaqahmed)
-
-
1 pull request opened.
-
Add Bluetooth to the list of policy-controlled features w3c/webappsec-permissions-policy#476, by @gabrielsanbrito.
-
-
1 pull request closed.
-
Add new permission policy features w3c/webappsec-permissions-policy#473.
-
w3c/webappsec
-
1 pull request opened.
-
Add Secure Curves in Web Crypto to meeting agenda w3c/webappsec#612, by @twiss.
-
-
1 pull request merged.
-
Add Secure Curves in Web Crypto to meeting agenda w3c/webappsec#612.
-
w3c/permissions-registry
-
1 issue received 1 new comment.
-
Removal of PermissionName broke downstream standards w3c/permissions-registry#11 (1 comment by @miketaylr)
-
w3c/permissions
-
1 issue closed.
-
"Changes to this document may be tracked at" points to incorrect repo ? w3c/permissions#198.
-
-
1 issue received 1 new comment.
-
"Changes to this document may be tracked at" points to incorrect repo ? w3c/permissions#198 (1 comment by @miketaylr)
-
w3c/webappsec-change-password-url
-
1 pull request merged.
-
Update README.md w3c/webappsec-change-password-url#38.
-
w3c/webappsec-referrer-policy
-
1 pull request closed.
-
Make 'unsafe-url' an alias for 'no-referrer-when-downgrade' w3c/webappsec-referrer-policy#124.
-
w3c/trusted-types
-
2 pull requests opened.
-
Remove callerRealm param from EnsureCSPDoesNotBlockStringCompilation w3c/trusted-types#370, by @antosart.
-
Fix prepare a script w3c/trusted-types#369, by @koto.
-
-
4 pull requests merged.
-
Remove callerRealm param from EnsureCSPDoesNotBlockStringCompilation w3c/trusted-types#370.
-
Remove Mike from the editors w3c/trusted-types#365.
-
Fix prepare a script w3c/trusted-types#369.
-
Fix minor inconsistencies w3c/trusted-types#361.
-
-
2 pull requests received 3 new comments.
-
Remove callerRealm param from EnsureCSPDoesNotBlockStringCompilation w3c/trusted-types#370 (2 comments by @antosart, @koto)
-
TR publications
-
3 documents published.
-
Permissions published 3 times as a Working Draft. History of Permissions
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Jonathan Hao (Google LLC) joined.
-
Mike Taylor (Google LLC) joined.
-
Johann Hofmann (Google LLC) joined.
-
GitHub
w3c/webappsec-fetch-metadata
-
1 issue received 2 new comments.
-
Extending the fetch metadata headers: related tabs/windows w3c/webappsec-fetch-metadata#83 (2 comments by @hemeryar, @mjz3)
-
w3c/webappsec-referrer-policy
-
2 issues closed.
-
Possible Version 2 w3c/webappsec-referrer-policy#143.
-
"Strip url for use as a referrer" sets path to null, which is a spec type error w3c/webappsec-referrer-policy#153.
-
-
2 issues received 5 new comments.
-
Add referrerpolicy to media elements (<audio> and <video>) w3c/webappsec-referrer-policy#160 (4 comments by @annevk, @dalecurtis, @domfarolino)
-
-
3 pull requests opened.
-
Remove Emily from the editors w3c/webappsec-referrer-policy#164, by @jyasskin.
-
Fix 'Strip url for use as referrer' to account for trailing slash w3c/webappsec-referrer-policy#163, by @domfarolino.
-
Fix 'Strip url for use as referrer' w3c/webappsec-referrer-policy#162, by @domfarolino.
-
-
4 pull requests merged.
-
Remove Emily from the editors w3c/webappsec-referrer-policy#164.
-
Fix 'Strip url for use as referrer' to account for trailing slash w3c/webappsec-referrer-policy#163.
-
Fix 'Strip url for use as referrer' w3c/webappsec-referrer-policy#162.
-
Remove Jochen from the editors w3c/webappsec-referrer-policy#161.
-
-
2 pull requests received 5 new comments.
-
Fix 'Strip url for use as referrer' w3c/webappsec-referrer-policy#162 (4 comments by @annevk, @domenic, @domfarolino)
-
Make 'unsafe-url' an alias for 'no-referrer-when-downgrade' w3c/webappsec-referrer-policy#124 (1 comment by @domfarolino)
-
w3c/webappsec-subresource-integrity
-
3 issues opened.
-
Consider adding integrity attribute to Link header w3c/webappsec-subresource-integrity#117, by @Pyrolistical.
-
Define equality comparator for metadata w3c/webappsec-subresource-integrity#116, by @noamr.
-
Be more specific about "most collision-resistant" w3c/webappsec-subresource-integrity#115, by @noamr.
-
-
1 issue closed.
-
Consider adding integrity attribute to Link header w3c/webappsec-subresource-integrity#117.
-
-
2 issues received 3 new comments.
-
Be more specific about "most collision-resistant" w3c/webappsec-subresource-integrity#115 (2 comments by @annevk, @mozfreddyb)
-
Consider adding integrity attribute to Link header w3c/webappsec-subresource-integrity#117 (1 comment by @noamr)
-
w3c/webcrypto
-
2 issues opened.
-
Allow `derivedKeyAlgorithm == 'HKDF'` for `deriveKey()` w3c/webcrypto#314, by @Treeston.
-
Add support for BLAKE2 (RFC7693) w3c/webcrypto#313, by @Jorropo.
-
-
3 issues received 5 new comments.
-
How to best propose features and show implementor interest w3c/webcrypto#280 (3 comments by @F1r3Hydr4nt, @TJKoury, @twiss)
-
PROPOSAL: Add support for general (hardware backed) cryptographic signatures and key exchange w3c/webcrypto#263 (1 comment by @stalek71)
-
Bug 27755 - Using the Subtle Crypto Interface with Streams w3c/webcrypto#73 (1 comment by @tniessen)
-
w3c/webappsec-permissions-policy
-
2 issues opened.
-
New permission policy features that should get a mention in this repo w3c/webappsec-permissions-policy#471, by @summercms.
-
PermissionsPolicyViolationReportBody is missing a toJSON operation w3c/webappsec-permissions-policy#469, by @foolip.
-
-
5 issues received 11 new comments.
-
Prevent programmatic focus in iframe w3c/webappsec-permissions-policy#273 (3 comments by @clelland, @marian-r)
-
Permissions Policy unload w3c/webappsec-permissions-policy#444 (3 comments by @annevk, @fergald, @jeffkaufman)
-
Proposal: define default for all w3c/webappsec-permissions-policy#189 (3 comments by @olmari, @Seirdy, @vphantom)
-
add "otp-credentials" policy-controlled feature token to features.md w3c/webappsec-permissions-policy#443 (1 comment by @summercms)
-
allow attribute prose and algorithm don't quite agree w3c/webappsec-permissions-policy#146 (1 comment by @chris-morgan)
-
-
3 pull requests opened.
-
Editorial: export * and 'self' w3c/webappsec-permissions-policy#474, by @marcoscaceres.
-
Add new permission policy features w3c/webappsec-permissions-policy#473, by @summercms.
-
Add PermissionsPolicyViolationReportBody toJSON operation w3c/webappsec-permissions-policy#472, by @antosart.
-
-
2 pull requests received 2 new comments.
w3c/permissions
-
2 issues closed.
-
Safari returns different results for current permission state w3c/permissions#278.
-
"Prompt the user to choose" should let caller decide how many results are allowed. w3c/permissions#375.
-
-
1 issue received 2 new comments.
-
Safari returns different results for current permission state w3c/permissions#278 (2 comments by @marcoscaceres, @miketaylr)
-
-
2 pull requests opened.
-
chore: Remove reference to issue #278 w3c/permissions#380, by @miketaylr.
-
editorial: Re-export the default permission query algorithm. w3c/permissions#378, by @jyasskin.
-
-
4 pull requests merged.
-
chore: Remove reference to issue #278 w3c/permissions#380.
-
Allow "prompt the user to choose" apply to one or more options. w3c/permissions#376.
-
Editorial: editorial pass on sections 5 and beyond w3c/permissions#374.
-
editorial: Re-export the default permission query algorithm. w3c/permissions#378.
-
-
3 pull requests received 15 new comments.
-
Allow "prompt the user to choose" apply to one or more options. w3c/permissions#376 (12 comments by @jyasskin, @marcoscaceres, @miketaylr)
-
Editorial: editorial pass on sections 5 and beyond w3c/permissions#374 (2 comments by @marcoscaceres, @miketaylr)
-
w3c/permissions#379 (1 comment by @w3cbot)
-
w3c/webappsec-cspee
-
1 issue opened.
-
Editor's draft not getting autoupdated w3c/webappsec-cspee#24, by @jyasskin.
-
-
2 pull requests opened.
-
Fix the Participate self-links w3c/webappsec-cspee#25, by @jyasskin.
-
Add Antonio Sartori as editor w3c/webappsec-cspee#23, by @antosart.
-
-
2 pull requests merged.
-
Fix the Participate self-links w3c/webappsec-cspee#25.
-
Add Antonio Sartori as editor w3c/webappsec-cspee#23.
-
w3c/permissions-registry
-
1 pull request opened.
-
fix: Chrome doesn't implement web-share w3c/permissions-registry#13, by @marcoscaceres.
-
-
1 pull request merged.
-
fix: Chrome doesn't implement web-share w3c/permissions-registry#13.
-
-
1 pull request received 1 new comment.
w3c/trusted-types
-
1 issue closed.
-
Create [TrustedTypes].fromLiteral method w3c/trusted-types#347.
-
-
1 issue reopened.
-
https://github.com/w3c/webappsec-trusted-types/issues/96#issuecomment-593651769 w3c/trusted-types#364, by @Truthofmanyis1.
-
-
1 pull request opened.
-
Remove Mike from the editors w3c/trusted-types#365, by @jyasskin.
-
w3c/webappsec-csp
-
3 issues opened.
-
CSPViolationReportBody is missing a toJSON operation w3c/webappsec-csp#546, by @foolip.
-
“Report a violation” can seemingly reach “fire an event at” w/ WorkletGlobalScope w3c/webappsec-csp#545, by @bathos.
-
`report-uri` deprecation timeline w3c/webappsec-csp#544, by @carlosjeurissen.
-
-
2 issues closed.
-
CSPViolationReportBody is missing a toJSON operation w3c/webappsec-csp#546.
-
Need a specific CSP policy for enabling WebAssembly execution w3c/webappsec-csp#443.
-
-
6 issues received 13 new comments.
-
“Report a violation” can seemingly reach “fire an event at” w/ WorkletGlobalScope w3c/webappsec-csp#545 (5 comments by @annevk, @antosart, @domenic)
-
Allow control over `dns-prefetch` and `preconnect` w3c/webappsec-csp#282 (2 comments by @mikewest, @noamr)
-
Need a specific CSP policy for enabling WebAssembly execution w3c/webappsec-csp#443 (1 comment by @dveditz)
-
-
2 pull requests opened.
-
Add CSPViolationReportBody toJSON operation w3c/webappsec-csp#547, by @antosart.
-
Add Antonio Sartori as editor w3c/webappsec-csp#543, by @antosart.
-
-
2 pull requests merged.
-
Add CSPViolationReportBody toJSON operation w3c/webappsec-csp#547.
-
Add Antonio Sartori as editor w3c/webappsec-csp#543.
-
-
1 pull request received 3 new comments.
-
Add CSPViolationReportBody toJSON operation w3c/webappsec-csp#547 (3 comments by @antosart, @foolip)
-
w3c/webappsec
-
1 pull request opened.
-
removing unused website mirror w3c/webappsec#610, by @samuelweiler.
-
-
2 pull requests merged.
-
removing unused website mirror w3c/webappsec#610.
-
Add 'A Well-Known URL for Changing Passwords' to the WG homepage. w3c/webappsec#609.
-
-
1 pull request closed.
-
Update index.html w3c/webappsec#605.
-
-
2 pull requests received 5 new comments.
-
Add 'A Well-Known URL for Changing Passwords' to the WG homepage. w3c/webappsec#609 (4 comments by @hober, @mikewest, @samuelweiler, @VojtaStanek)
-
w3c/webappsec-change-password-url
-
1 issue opened.
-
Be explicit that this specification is about "changing a password", not "resetting a password" w3c/webappsec-change-password-url#39, by @danieljrmay.
-
-
1 pull request opened.
-
Add Backdrop CMS as a tool which implements this standard w3c/webappsec-change-password-url#40, by @danieljrmay.
-
-
1 pull request merged.
-
Add Backdrop CMS as a tool which implements this standard w3c/webappsec-change-password-url#40.
-
-
2 pull requests received 2 new comments.
-
Add Backdrop CMS as a tool which implements this standard w3c/webappsec-change-password-url#40 (1 comment by @w3cbot)
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Nicolas Pena Moreno (Google LLC) joined.
-
-
1 participant left.
-
Marcos Caceres (Apple Inc.) left.
-
GitHub
w3c/webappsec
-
2 issues received 2 new comments.
-
CSP: Consider a flag to turn off console logging for Report-Only w3c/webappsec#508 (1 comment by @swijckmans)
-
1 pull request opened.
-
Add 'A Well-Known URL for Changing Passwords' to the WG homepage. w3c/webappsec#609, by @hober.
-
w3c/webappsec-referrer-policy
-
1 issue opened.
-
Add referrerpolicy to media elements (<audio> and <video>) w3c/webappsec-referrer-policy#160, by @SegaraRai.
-
-
1 pull request opened.
-
Remove Jochen from the editors w3c/webappsec-referrer-policy#161, by @jyasskin.
-
w3c/webappsec-mixed-content
-
1 pull request opened.
-
Make Mike a former editor w3c/webappsec-mixed-content#60, by @jyasskin.
-
w3c/webappsec-credential-management
-
1 issue closed.
-
Throw exceptions in Credential internal methods w3c/webappsec-credential-management#197.
-
-
1 issue received 1 new comment.
-
Permissions Policy vs. sameOriginWithAncestors checks w3c/webappsec-credential-management#195 (1 comment by @johannhof)
-
-
1 pull request opened.
-
Mark Jeff as a former editor w3c/webappsec-credential-management#198, by @jyasskin.
-
-
2 pull requests merged.
-
Mark Jeff as a former editor w3c/webappsec-credential-management#198.
-
Throw exceptions instead of returning them w3c/webappsec-credential-management#196.
-
-
1 pull request received 1 new comment.
-
Throw exceptions instead of returning them w3c/webappsec-credential-management#196 (1 comment by @nidhijaju)
-
w3c/webappsec-permissions-policy
-
2 issues received 6 new comments.
-
Support for declaring feature policy in HTML w3c/webappsec-permissions-policy#55 (4 comments by @annevk, @dmarti, @npdoty)
-
Proposal: define default for all w3c/webappsec-permissions-policy#189 (2 comments by @jsleeio, @PeteX)
-
-
3 pull requests opened.
-
Add local-fonts permission policy w3c/webappsec-permissions-policy#458, by @inexorabletash.
-
Fix broken list items w3c/webappsec-permissions-policy#453, by @eeeps.
-
Export all algorithms (as algorithms) w3c/webappsec-permissions-policy#451, by @eeeps.
-
-
3 pull requests merged.
-
Fix broken list items w3c/webappsec-permissions-policy#453.
-
Export all algorithms (as algorithms) w3c/webappsec-permissions-policy#451.
-
Update feature table for hid, idle-detection and serial w3c/webappsec-permissions-policy#448.
-
-
3 pull requests received 10 new comments.
-
Export all algorithms (as algorithms) w3c/webappsec-permissions-policy#451 (7 comments by @clelland, @eeeps, @johannhof)
-
Add local-fonts permission policy w3c/webappsec-permissions-policy#458 (2 comments by @freddieleeman, @inexorabletash)
-
w3c/webappsec-csp
-
4 issues received 7 new comments.
-
Consider relaxing `prefetch-src` and preload `as` w3c/webappsec-csp#542 (2 comments by @hiroshige-g, @noamr)
-
-
3 pull requests merged.
-
Introduce 'webrtc' as a simple on/off switch w3c/webappsec-csp#457.
-
Remove calleeRealm from EnsureCSPDoesNotBlockWasmByteCompilation w3c/webappsec-csp#526.
-
Remove callerRealm param from EnsureCSPDoesNotBlockStringCompilation w3c/webappsec-csp#541.
-
-
2 pull requests received 11 new comments.
-
Remove calleeRealm from EnsureCSPDoesNotBlockWasmByteCompilation w3c/webappsec-csp#526 (2 comments by @antosart)
w3c/webappsec-subresource-integrity
-
1 issue opened.
-
Apply subresource integrity to <img> tags w3c/webappsec-subresource-integrity#113, by @mlissner.
-
w3c/permissions
-
1 issue opened.
-
Gaps in the current permissions model w3c/permissions#377, by @miketaylr.
-
-
2 issues received 5 new comments.
-
1 pull request opened.
-
Allow "prompt the user to choose" apply to one or more options. w3c/permissions#376, by @miketaylr.
-
-
1 pull request received 2 new comments.
-
Allow "prompt the user to choose" apply to one or more options. w3c/permissions#376 (2 comments by @jyasskin)
-
w3c/trusted-types
-
1 issue received 1 new comment.
-
Can we conditionally enforce Trusted Types based on document response type in XHR? w3c/trusted-types#360 (1 comment by @securityMB)
-
w3c/webappsec-clear-site-data
-
1 issue received 2 new comments.
w3c/webappsec-secure-contexts
-
1 issue received 1 new comment.
-
Using secure-context gated features with local devices w3c/webappsec-secure-contexts#60 (1 comment by @aerik)
-
TR publications
-
2 documents published.
-
Permissions published twice as a Working Draft. History of Permissions
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Bartosz Niemczura (Meta) joined.
-
-
1 participant left.
-
Jeff Hodges (Google LLC) left.
-
GitHub
w3c/webappsec-permissions-policy
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
Update feature table for hid, idle-detection and serial w3c/webappsec-permissions-policy#448, by @reillyeon.
-
Replace usage of "responsible document" w3c/webappsec-permissions-policy#447, by @johannhof.
-
Replace outdated references in integration.md w3c/webappsec-permissions-policy#446, by @johannhof.
-
-
3 pull requests merged.
-
Replace usage of "responsible document" w3c/webappsec-permissions-policy#447.
-
Replace outdated references in integration.md w3c/webappsec-permissions-policy#446.
-
Add browsing-topics to experimental features list w3c/webappsec-permissions-policy#445.
-
-
3 pull requests received 6 new comments.
-
Replace usage of "responsible document" w3c/webappsec-permissions-policy#447 (3 comments by @clelland, @johannhof)
-
Replace outdated references in integration.md w3c/webappsec-permissions-policy#446 (2 comments by @clelland, @johannhof)
-
Add browsing-topics to experimental features list w3c/webappsec-permissions-policy#445 (1 comment by @w3cbot)
-
w3c/webappsec-credential-management
-
3 issues opened.
-
Throw exceptions in Credential internal methods w3c/webappsec-credential-management#197, by @nidhijaju.
-
Permissions Policy vs. sameOriginWithAncestors checks w3c/webappsec-credential-management#195, by @johannhof.
-
add concept of credential source backup (sync) w3c/webappsec-credential-management#194, by @equalsJeffH.
-
-
1 issue closed.
-
Permissions Policy vs. sameOriginWithAncestors checks w3c/webappsec-credential-management#195.
-
-
1 issue received 1 new comment.
-
Permissions Policy vs. sameOriginWithAncestors checks w3c/webappsec-credential-management#195 (1 comment by @nsatragno)
-
-
2 pull requests opened.
-
Throw exceptions instead of returning them w3c/webappsec-credential-management#196, by @nidhijaju.
-
Editorial: use associated Document in place of responsible document w3c/webappsec-credential-management#193, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/webappsec-credential-management#193.
-
-
2 pull requests received 17 new comments.
-
Throw exceptions instead of returning them w3c/webappsec-credential-management#196 (15 comments by @nidhijaju, @nsatragno)
-
Editorial: use associated Document in place of responsible document w3c/webappsec-credential-management#193 (2 comments by @miketaylr)
-
w3c/webcrypto
-
1 issue opened.
-
Ambiguity of the Web Crypto API Doc w3c/webcrypto#310, by @ShiqiHe000.
-
-
4 issues received 18 new comments.
-
How to best propose features and show implementor interest w3c/webcrypto#280 (9 comments by @panva, @TJKoury, @tniessen, @twiss)
-
Bug 27774 - The KDFs either shouldn't allow importing extractable keys, or should support exportKey() w3c/webcrypto#76 (7 comments by @ghost, @twiss)
-
Test importing spki and pkcs8 keys with algorithm-specific OIDs w3c/webcrypto#307 (1 comment by @twiss)
-
-
1 pull request opened.
-
fix PBKDF2 get key length w3c/webcrypto#311, by @panva.
-
-
2 pull requests merged.
-
fix PBKDF2 get key length w3c/webcrypto#311.
-
Use shorthand forms instead of <var> and <code> elements w3c/webcrypto#309.
-
-
1 pull request received 1 new comment.
w3c/webappsec-clear-site-data
-
1 issue opened.
-
Clear-Site-Data and bfcache w3c/webappsec-clear-site-data#73, by @domenic.
-
-
1 issue received 1 new comment.
w3c/trusted-types
-
2 issues opened.
-
Figure out if there is a better way to guard navigations to `javascript:` across documents w3c/trusted-types#363, by @koto.
-
Jquery Js getting reported error with TrustedTypes implementation w3c/trusted-types#362, by @vijaysn2702.
-
-
1 issue closed.
-
Jquery Js getting reported error with TrustedTypes implementation w3c/trusted-types#362.
-
-
2 issues received 4 new comments.
-
Add SVG <use> href attribute to Trusted Types enforcement w3c/trusted-types#357 (3 comments by @annevk, @shhnjk)
-
Jquery Js getting reported error with TrustedTypes implementation w3c/trusted-types#362 (1 comment by @koto)
-
-
1 pull request opened.
-
Fix minor inconsistencies w3c/trusted-types#361, by @Siegrift.
-
-
1 pull request received 2 new comments.
w3c/permissions
-
1 issue opened.
-
"Prompt the user to choose" should let caller decide how many results are allowed. w3c/permissions#375, by @jyasskin.
-
-
1 issue closed.
-
"extra permission data" definition should be normative w3c/permissions#369.
-
-
4 issues received 4 new comments.
-
"Prompt the user to choose" should let caller decide how many results are allowed. w3c/permissions#375 (1 comment by @miketaylr)
-
Add a fourth permission state "grantable without a prompt"? w3c/permissions#250 (1 comment by @miketaylr)
-
Provide guidelines or heuristics to prevent fingerprinting in case permission is denied w3c/permissions#361 (1 comment by @youennf)
-
"extra permission data" definition should be normative w3c/permissions#369 (1 comment by @miketaylr)
-
-
4 pull requests opened.
-
Editorial: editorial pass on sections 5 and beyond w3c/permissions#374, by @miketaylr.
-
Editorial: take an editorial pass at section 4 w3c/permissions#373, by @miketaylr.
-
Editorial: Do an editorial pass on first 3 sections w3c/permissions#371, by @miketaylr.
-
Editorial: move [=extra permission data=] out of example w3c/permissions#370, by @miketaylr.
-
-
3 pull requests merged.
-
Editorial: take an editorial pass at section 4 w3c/permissions#373.
-
Editorial: Do an editorial pass on first 3 sections w3c/permissions#371.
-
Editorial: move [=extra permission data=] out of example w3c/permissions#370.
-
-
2 pull requests received 3 new comments.
w3c/webappsec-fetch-metadata
-
1 issue opened.
-
Extending the fetch metadata headers: related tabs/windows w3c/webappsec-fetch-metadata#83, by @mjz3.
-
-
1 issue received 1 new comment.
-
Extending the fetch metadata headers: related tabs/windows w3c/webappsec-fetch-metadata#83 (1 comment by @annevk)
-
w3c/webappsec-upgrade-insecure-requests
-
1 issue opened.
-
Update usage of "responsible document" and "responsible browsing context". w3c/webappsec-upgrade-insecure-requests#27, by @miketaylr.
-
w3c/webappsec-mixed-content
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/webappsec-mixed-content#59, by @miketaylr.
-
w3c/webappsec-csp
-
1 issue opened.
-
Consider relaxing `prefetch-src` and preload `as` w3c/webappsec-csp#542, by @noamr.
-
-
2 issues received 4 new comments.
-
Consider relaxing `prefetch-src` and preload `as` w3c/webappsec-csp#542 (2 comments by @annevk, @noamr)
-
w3c/permissions-registry
-
3 issues closed.
-
Should the registry include policy-controlled features? w3c/permissions-registry#7.
-
Description of criteria for inclusion w3c/permissions-registry#8.
-
Add Purpose section w3c/permissions-registry#10.
-
-
1 issue received 1 new comment.
-
Removal of PermissionName broke downstream standards w3c/permissions-registry#11 (1 comment by @beaufortfrancois)
-
-
1 pull request opened.
-
Generalize to Permissions Registry w3c/permissions-registry#12, by @marcoscaceres.
-
-
1 pull request merged.
-
Generalize to Permissions Registry w3c/permissions-registry#12.
-
-
1 pull request received 10 new comments.
-
Generalize to Permissions Registry w3c/permissions-registry#12 (10 comments by @marcoscaceres, @miketaylr)
-
TR publications
-
10 documents published.
-
Permissions published 10 times as a Working Draft. History of Permissions
-
Past meetings
-
1 meeting.
GitHub
w3c/webappsec-csp
-
2 issues opened.
-
Eval, callerRealm and calleeRealm w3c/webappsec-csp#539, by @antosart.
-
What should the default be for the "webrtc" directive in workers? w3c/webappsec-csp#538, by @alvestrand.
-
-
1 issue closed.
-
Eval, callerRealm and calleeRealm w3c/webappsec-csp#539.
-
-
6 issues received 12 new comments.
-
Cross-realm eval() calls and 'unsafe-eval' w3c/webappsec-csp#438 (3 comments by @annevk, @antosart, @domenic)
-
Eval, callerRealm and calleeRealm w3c/webappsec-csp#539 (3 comments by @annevk, @antosart, @domenic)
-
Allow control over `dns-prefetch` and `preconnect` w3c/webappsec-csp#282 (2 comments by @ianopolous, @yoavweiss)
-
Should Workers inherit CSP directives from the parent context? w3c/webappsec-csp#336 (2 comments by @antosart, @oliverdunk)
-
What should the default be for the "webrtc" directive in workers? w3c/webappsec-csp#538 (1 comment by @antosart)
-
Include script hash in CSP report when 'report-sample' is set w3c/webappsec-csp#378 (1 comment by @gabinkbl)
-
-
2 pull requests opened.
-
Remove callerRealm param from EnsureCSPDoesNotBlockStringCompilation w3c/webappsec-csp#541, by @antosart.
-
Do not check callerRealm for eval w3c/webappsec-csp#540, by @antosart.
-
-
1 pull request merged.
-
Do not check callerRealm for eval w3c/webappsec-csp#540.
-
-
4 pull requests received 19 new comments.
-
Introduce 'webrtc' as a simple on/off switch w3c/webappsec-csp#457 (13 comments by @annevk, @antosart, @jan-ivar, @martinthomson, @zenhack)
-
Remove calleeRealm from EnsureCSPDoesNotBlockWasmByteCompilation w3c/webappsec-csp#526 (2 comments by @antosart)
-
Remove callerRealm param from EnsureCSPDoesNotBlockStringCompilation w3c/webappsec-csp#541 (1 comment by @antosart)
-
w3c/permissions
-
3 issues opened.
-
"extra permission data" definition should be normative w3c/permissions#369, by @dontcallmedom.
-
Provide guidelines or heuristics to prevent fingerprinting in case permission is denied w3c/permissions#361, by @youennf.
-
Further alignment with Permissions Policy w3c/permissions#356, by @marcoscaceres.
-
-
8 issues closed.
-
Specifications should add conformance classes w3c/permissions#283.
-
Handle non-fully-active documents w3c/permissions#162.
-
Permissions states should be concepts w3c/permissions#243.
-
Add "background-playback" permission type? w3c/permissions#193.
-
Move permissions out to each spec w3c/permissions#263.
-
Proposals: Drop "Powerful features registry" and PermissionName enum w3c/permissions#314.
-
Definition of PermissionStatus lifetime w3c/permissions#266.
-
-
10 issues received 17 new comments.
-
Safari returns different results for current permission state w3c/permissions#278 (3 comments by @jyasskin, @miketaylr)
-
Provide guidelines or heuristics to prevent fingerprinting in case permission is denied w3c/permissions#361 (2 comments by @jyasskin, @KOLANICH)
-
Guidance on whether to add a permissions to the platform w3c/permissions#116 (1 comment by @marcoscaceres)
-
Proposals: Drop "Powerful features registry" and PermissionName enum w3c/permissions#314 (1 comment by @marcoscaceres)
-
Add a fourth permission state "grantable without a prompt"? w3c/permissions#250 (1 comment by @miketaylr)
-
17 pull requests opened.
-
Editorial: add UA + spec conformance classes w3c/permissions#368, by @marcoscaceres.
-
Editorial: clarify Permissions Policy / Powerful Feature overlap w3c/permissions#367, by @marcoscaceres.
-
Handle non-fully-active documents w3c/permissions#365, by @marcoscaceres.
-
Editorial: Add linking-text for "specifies a powerful feature" w3c/permissions#363, by @miketaylr.
-
Add requirements for specifying Powerful Features w3c/permissions#362, by @marcoscaceres.
-
Simplify GC model w3c/permissions#360, by @marcoscaceres.
-
Editorial: generalize statement about PermissionState emum w3c/permissions#359, by @marcoscaceres.
-
Editorial: make 'Creating instances' an algorithm w3c/permissions#357, by @marcoscaceres.
-
Editorial: cleanup Permissions model w3c/permissions#355, by @marcoscaceres.
-
Add concept of Default Permission State w3c/permissions#354, by @marcoscaceres.
-
Switch PermissionName to DOMString w3c/permissions#353, by @marcoscaceres.
-
Editorial: run 'in parallel', not asynchronously w3c/permissions#352, by @marcoscaceres.
-
Editorial: clean up Relationship to Permissions Policy w3c/permissions#351, by @marcoscaceres.
-
Editorial: cleanup examples w3c/permissions#350, by @marcoscaceres.
-
Editorial: bring back Automated Testing into spec w3c/permissions#346, by @marcoscaceres.
-
Editorial: clean up abstract w3c/permissions#345, by @marcoscaceres.
-
Split Pri/Sec considerations + give user control over features w3c/permissions#344, by @marcoscaceres.
-
-
17 pull requests merged.
-
Editorial: clarify Permissions Policy / Powerful Feature overlap w3c/permissions#367.
-
Editorial: add UA + spec conformance classes w3c/permissions#368.
-
Handle non-fully-active documents w3c/permissions#365.
-
Editorial: Add linking-text for "specifies a powerful feature" w3c/permissions#363.
-
Editorial: bring back Automated Testing into spec w3c/permissions#346.
-
Add requirements for specifying Powerful Features w3c/permissions#362.
-
Switch PermissionName to DOMString w3c/permissions#353.
-
Simplify GC model w3c/permissions#360.
-
Editorial: generalize statement about PermissionState emum w3c/permissions#359.
-
Editorial: make 'Creating instances' an algorithm w3c/permissions#357.
-
Editorial: clean up Relationship to Permissions Policy w3c/permissions#351.
-
Editorial: cleanup Permissions model w3c/permissions#355.
-
Editorial: clean up abstract w3c/permissions#345.
-
Add concept of Default Permission State w3c/permissions#354.
-
Editorial: run 'in parallel', not asynchronously w3c/permissions#352.
-
Editorial: cleanup examples w3c/permissions#350.
-
Split Pri/Sec considerations + give user control over features w3c/permissions#344.
-
-
4 pull requests closed.
-
feat(prompts): allow UAs to deny non-gesture prompts w3c/permissions#107.
-
Handle not fully active documents when querying Permissions API w3c/permissions#249.
-
Editorial: use permission state concept, not enum values w3c/permissions#285.
-
Rename PermissionName enum to PowerfulFeatureName w3c/permissions#286.
-
-
15 pull requests received 45 new comments.
-
Add requirements for specifying Powerful Features w3c/permissions#362 (7 comments by @marcoscaceres, @miketaylr)
-
Editorial: clean up Relationship to Permissions Policy w3c/permissions#351 (5 comments by @marcoscaceres, @miketaylr)
-
Editorial: clarify Permissions Policy / Powerful Feature overlap w3c/permissions#367 (4 comments by @kenchris, @marcoscaceres, @miketaylr)
-
Editorial: bring back Automated Testing into spec w3c/permissions#346 (2 comments by @marcoscaceres, @miketaylr)
-
Handle not fully active documents when querying Permissions API w3c/permissions#249 (1 comment by @marcoscaceres)
-
Editorial: Add linking-text for "specifies a powerful feature" w3c/permissions#363 (1 comment by @miketaylr)
-
w3c/permissions#358 (1 comment by @w3cbot)
-
Split Pri/Sec considerations + give user control over features w3c/permissions#344 (1 comment by @marcoscaceres)
-
w3c/webcrypto
-
1 issue opened.
-
make the api string and base64 friendly w3c/webcrypto#308, by @r-jo.
-
-
1 issue closed.
-
make the api string and base64 friendly w3c/webcrypto#308.
-
-
2 issues received 11 new comments.
-
make the api string and base64 friendly w3c/webcrypto#308 (7 comments by @panva, @r-jo, @tniessen, @twiss)
-
Do not mandate secure context for SubtleCrypto w3c/webcrypto#170 (4 comments by @bradisbell, @twiss)
-
-
1 pull request opened.
-
Use shorthand forms instead of <var> and <code> elements w3c/webcrypto#309, by @twiss.
-
w3c/trusted-types
-
4 issues opened.
-
Can we conditionally enforce Trusted Types based on document response type in XHR? w3c/trusted-types#360, by @shhnjk.
-
Maybe enforce Trusted Types in XSL's xsl:text w3c/trusted-types#359, by @shhnjk.
-
Maybe enforce Trusted Types in document.createProcessingInstruction? w3c/trusted-types#358, by @shhnjk.
-
Add SVG <use> href attribute to Trusted Types enforcement w3c/trusted-types#357, by @shhnjk.
-
-
3 issues received 13 new comments.
-
Add SVG <use> href attribute to Trusted Types enforcement w3c/trusted-types#357 (10 comments by @annevk, @koto, @masatokinugawa, @mikewest, @mozfreddyb)
-
Can we conditionally enforce Trusted Types based on document response type in XHR? w3c/trusted-types#360 (1 comment by @craigfrancis)
-
w3c/webappsec-permissions-policy
-
2 issues received 11 new comments.
-
Permissions Policy unload w3c/webappsec-permissions-policy#444 (10 comments by @annevk, @fergald, @johannhof)
-
-
1 pull request opened.
-
Add browsing-topics to experimental features list w3c/webappsec-permissions-policy#445, by @freddieleeman.
-
-
2 pull requests closed.
-
Add interest-cohort to list of Experimental Features w3c/webappsec-permissions-policy#437.
-
Add interest-cohort to features list w3c/webappsec-permissions-policy#420.
-
-
2 pull requests received 3 new comments.
-
Add interest-cohort to features list w3c/webappsec-permissions-policy#420 (2 comments by @bershanskiy, @freddieleeman)
-
Add interest-cohort to list of Experimental Features w3c/webappsec-permissions-policy#437 (1 comment by @freddieleeman)
-
w3c/webappsec-change-password-url
-
1 issue received 2 new comments.
-
Any follow-up drafts for fully automated password change? w3c/webappsec-change-password-url#34 (2 comments by @dumblob, @oliverdunk)
-
-
2 pull requests opened.
-
Update README.md w3c/webappsec-change-password-url#38, by @vasilii-sv.
-
Add 1Password w3c/webappsec-change-password-url#37, by @oliverdunk.
-
-
1 pull request merged.
-
Add 1Password w3c/webappsec-change-password-url#37.
-
-
2 pull requests received 3 new comments.
w3c/webappsec-clear-site-data
-
1 issue received 1 new comment.
w3c/permissions-registry
-
7 issues opened.
-
Removal of PermissionName broke downstream standards w3c/permissions-registry#11, by @annevk.
-
Add Purpose section w3c/permissions-registry#10, by @marcoscaceres.
-
Description of criteria for inclusion w3c/permissions-registry#8, by @marcoscaceres.
-
Should the registry include policy-controlled features? w3c/permissions-registry#7, by @marcoscaceres.
-
Other example than sync-xhr? w3c/permissions-registry#6, by @annevk.
-
CFC for publication as a "Draft Registry" w3c/permissions-registry#4, by @marcoscaceres.
-
Editorial pass w3c/permissions-registry#3, by @marcoscaceres.
-
-
2 issues closed.
-
Other example than sync-xhr? w3c/permissions-registry#6.
-
Editorial pass w3c/permissions-registry#3.
-
-
5 issues received 36 new comments.
-
Should the registry include policy-controlled features? w3c/permissions-registry#7 (12 comments by @annevk, @clelland, @marcoscaceres)
-
Other example than sync-xhr? w3c/permissions-registry#6 (10 comments by @annevk, @dveditz, @marcoscaceres)
-
Description of criteria for inclusion w3c/permissions-registry#8 (7 comments by @marcoscaceres, @miketaylr)
-
Removal of PermissionName broke downstream standards w3c/permissions-registry#11 (3 comments by @annevk, @marcoscaceres)
-
-
4 pull requests opened.
-
Editorial: rework example w3c/permissions-registry#9, by @marcoscaceres.
-
Add Change Process w3c/permissions-registry#5, by @marcoscaceres.
-
chore: setup publishing workflows w3c/permissions-registry#2, by @marcoscaceres.
-
Create initial registry w3c/permissions-registry#1, by @marcoscaceres.
-
-
4 pull requests merged.
-
Editorial: rework example w3c/permissions-registry#9.
-
Add Change Process w3c/permissions-registry#5.
-
chore: setup publishing workflows w3c/permissions-registry#2.
-
Create initial registry w3c/permissions-registry#1.
-
-
1 pull request received 5 new comments.
w3c/webappsec-credential-management
-
5 issues opened.
-
Make [[Create]] consistently create its Credentials from a task w3c/webappsec-credential-management#192, by @jyasskin.
-
normal use case is 1 person per browser per domain and hence 1 single account per browser per domain w3c/webappsec-credential-management#190, by @r-jo.
-
id field should be optional w3c/webappsec-credential-management#189, by @r-jo.
-
is it necessary?: if (credential.type == 'password') w3c/webappsec-credential-management#188, by @r-jo.
-
-
4 issues closed.
-
normal use case is 1 person per browser per domain and hence 1 single account per browser per domain w3c/webappsec-credential-management#190.
-
is it necessary?: if (credential.type == 'password') w3c/webappsec-credential-management#188.
-
id field should be optional w3c/webappsec-credential-management#189.
-
security w3c/webappsec-credential-management#191.
-
-
1 issue received 2 new comments.
-
normal use case is 1 person per browser per domain and hence 1 single account per browser per domain w3c/webappsec-credential-management#190 (2 comments by @r-jo)
-
w3c/webappsec-subresource-integrity
-
1 pull request received 6 new comments.
-
Update references and clarify section 3.5 in the current version of the spec w3c/webappsec-subresource-integrity#112 (6 comments by @annevk, @baek9)
-
TR publications
-
1 document published.
-
Permissions published as a Working Draft. History of Permissions
-
Participants
-
1 participant joined.
-
lawil karama (Snake Nation) joined.
-
-
1 organization joined.
-
Snake Nation joined.
-
-
1 organization left.
-
Baycloud Systems left.
-
GitHub
w3c/webappsec-csp
-
2 issues opened.
-
match-source-expression appears to be missing from CSP2 and CSP3 w3c/webappsec-csp#537, by @3lixy.
-
definitions of ancestor-source differ between documents w3c/webappsec-csp#535, by @kgoess.
-
-
1 issue closed.
-
match-source-expression appears to be missing from CSP2 and CSP3 w3c/webappsec-csp#537.
-
-
2 issues received 3 new comments.
-
match-source-expression appears to be missing from CSP2 and CSP3 w3c/webappsec-csp#537 (2 comments by @3lixy, @antosart)
-
definitions of ancestor-source differ between documents w3c/webappsec-csp#535 (1 comment by @annevk)
-
-
1 pull request opened.
-
[auto-publish] Fail only on link-error w3c/webappsec-csp#536, by @antosart.
-
-
1 pull request merged.
-
[auto-publish] Fail only on link-error w3c/webappsec-csp#536.
-
-
3 pull requests received 27 new comments.
-
Introduce 'webrtc' as a simple on/off switch w3c/webappsec-csp#457 (24 comments by @alvestrand, @annevk, @antosart, @zenhack)
-
Minimal specification of 'wasm-unsafe-eval' source directive w3c/webappsec-csp#293 (2 comments by @firstdorsal, @fosskers)
-
w3c/webappsec
-
1 issue closed.
-
Admin w3c/webappsec#608.
-
w3c/webappsec-permissions-policy
-
1 issue opened.
-
Permissions Policy unload w3c/webappsec-permissions-policy#444, by @fergald.
-
-
1 issue received 1 new comment.
w3c/trusted-types
-
2 pull requests opened.
-
Fix typo in README.md w/r/t ES Modules import w3c/trusted-types#356, by @Zemnmez.
-
Added fromLiteral implementation to the polyfill w3c/trusted-types#355, by @koto.
-
-
2 pull requests merged.
-
Fix typo in README.md w/r/t ES Modules import w3c/trusted-types#356.
-
Added fromLiteral implementation to the polyfill w3c/trusted-types#355.
-
-
1 pull request received 2 new comments.
w3c/webcrypto
-
1 issue closed.
-
Use `rsaEncryption` OID during exporting for all RSA algorithms w3c/webcrypto#300.
-
-
3 issues received 10 new comments.
-
Bug 27755 - Using the Subtle Crypto Interface with Streams w3c/webcrypto#73 (7 comments by @dead-claudia, @jfbrennan, @lucacasonato, @twiss)
-
PROPOSAL: Add support for general (hardware backed) cryptographic signatures and key exchange w3c/webcrypto#263 (1 comment by @dcow)
-
-
2 pull requests merged.
-
add randomUUID method w3c/webcrypto#285.
-
Update RSA and ECDH export steps and OIDs w3c/webcrypto#305.
-
-
1 pull request received 7 new comments.
w3c/webappsec-subresource-integrity
-
1 issue received 2 new comments.
-
The algorithm for parsing metadata should be described in more detail w3c/webappsec-subresource-integrity#84 (2 comments by @annevk, @baek9)
-
-
2 pull requests opened.
-
Update references and clarify section 3.5 in the current version of the spec w3c/webappsec-subresource-integrity#112, by @baek9.
-
Fix a misaligned index number w3c/webappsec-subresource-integrity#111, by @baek9.
-
-
1 pull request merged.
-
Fix a misaligned index number w3c/webappsec-subresource-integrity#111.
-
-
3 pull requests received 40 new comments.
-
Edit 3.3.2 Parse metadata in more detail w3c/webappsec-subresource-integrity#110 (30 comments by @annevk, @baek9, @mozfreddyb)
-
Update references and clarify section 3.5 in the current version of the spec w3c/webappsec-subresource-integrity#112 (7 comments by @annevk, @baek9, @mozfreddyb)
-
Fix a misaligned index number w3c/webappsec-subresource-integrity#111 (3 comments by @baek9, @mozfreddyb, @w3cbot)
-
w3c/permissions
-
1 issue closed.
-
Ensure "speaker-selection" is integrated into Audio Output Devices API spec w3c/permissions#320.
-
-
2 issues received 2 new comments.
-
Interaction between browser and system permissions w3c/permissions#332 (1 comment by @marcoscaceres)
-
Ensure "speaker-selection" is integrated into Audio Output Devices API spec w3c/permissions#320 (1 comment by @miketaylr)
-
-
1 pull request merged.
-
Editorial: relocate nfc powerful feature. w3c/permissions#336.
-
w3c/webappsec-credential-management
-
1 issue opened.
-
W3C policy requires Privacy Considerations and Security Considerations to be separate sections w3c/webappsec-credential-management#186, by @equalsJeffH.
-
-
3 issues closed.
-
W3C policy requires Privacy Considerations and Security Considerations to be separate sections w3c/webappsec-credential-management#186.
-
`publicKey` member identifier in Options should be `"public-key"`, or vice-versa? w3c/webappsec-credential-management#147.
-
add permissions policy support for webauthn w3c/webappsec-credential-management#136.
-
-
2 pull requests opened.
-
create separate security and privacy considerations sections w3c/webappsec-credential-management#187, by @equalsJeffH.
-
Use the registry to find interface objects for a CredentalOptions. w3c/webappsec-credential-management#185, by @equalsJeffH.
-
-
4 pull requests merged.
-
create separate security and privacy considerations sections w3c/webappsec-credential-management#187.
-
Map options member identifiers and credential types: public-key vs publicKey w3c/webappsec-credential-management#181.
-
Use the registry to find interface objects for a CredentalOptions. w3c/webappsec-credential-management#185.
-
Add permissions-policy check for publicKey credentials w3c/webappsec-credential-management#182.
-
-
3 pull requests received 16 new comments.
-
Map options member identifiers and credential types: public-key vs publicKey w3c/webappsec-credential-management#181 (7 comments by @equalsJeffH, @jyasskin)
-
Add permissions-policy check for publicKey credentials w3c/webappsec-credential-management#182 (7 comments by @equalsJeffH, @jyasskin, @kenrb)
-
create separate security and privacy considerations sections w3c/webappsec-credential-management#187 (2 comments by @equalsJeffH)
-
w3c/webappsec-secure-contexts
-
1 issue received 4 new comments.
-
Using secure-context gated features with local devices w3c/webappsec-secure-contexts#60 (4 comments by @jharris1993, @pinobatch)
-
w3c/webappsec-clear-site-data
-
1 issue opened.
-
Update Clear-Site-Data for partitioned cookies w3c/webappsec-clear-site-data#72, by @jyasskin.
-
-
1 issue received 1 new comment.
-
Update Clear-Site-Data for partitioned cookies w3c/webappsec-clear-site-data#72 (1 comment by @jyasskin)
-