-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Planning the 2024-03-20 meeting #643
Comments
I'd also like to discuss Curve25519 indeed, as well as a proposal for other modern algorithms in Web Crypto, and feature detection (e.g. |
I'd like to discuss about adding reports for iframes into Permissions Policy: w3c/webappsec-permissions-policy#537 |
I'd also like to continue the discussion on this PR around the WebAppSec Mitigations Wiki and where the most appropriate permanent home for this information might be. |
agenda+ TPAC 2024: webappsec meeting? [[
Each group will be able to ask for 90-minute and/or 2-hour slots. You may ask for several slots. |
agenda+ Introducing @simoneonofri , new W3C Web Security Lead |
Recording the current state of #643.
Could we add w3c/webappsec-csp#651 to the agenda please, sorry it's a bit late. |
And also could we add w3c/trusted-types#221 please. |
@lukewarlow: I'll add these to the agenda. @camillelamy: I'll add https://github.com/explainers-by-googlers/document-isolation-policy/ as well, per our conversation elsewhere. |
Planning the 2024-03-20 WebAppSec meeting. Please add potential topics below
The text was updated successfully, but these errors were encountered: