Security Interest Group - Activity in 2022
No matches.
GitHub
w3c/security-questionnaire
-
2 pull requests opened.
-
Create CODE_OF_CONDUCT.md w3c/security-questionnaire#149, by @torgo.
-
Create LICENCE (CC0) w3c/security-questionnaire#148, by @torgo.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
1 pull request received 24 new comments.
-
Rewrite the BFCache question w3c/security-questionnaire#144 (24 comments by @annevk, @domenic, @rakina, @smaug----)
-
GitHub
w3c/security-questionnaire
-
3 issues opened.
-
make "capability doesn't exist" and "permission denied" look the same w3c/security-questionnaire#147, by @samuelweiler.
-
ephemeral fingerprinting w3c/security-questionnaire#146, by @samuelweiler.
-
cite design principle re: make private mode undetectable w3c/security-questionnaire#145, by @samuelweiler.
-
-
1 pull request received 3 new comments.
GitHub
w3c/security-questionnaire
-
1 pull request opened.
-
Rewrite the BFCache question w3c/security-questionnaire#144, by @rakina.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
1 pull request opened.
-
Use the w3.org version of How to do Wide Review w3c/security-questionnaire#143, by @xfq.
-
GitHub
w3c/security-questionnaire
-
1 pull request opened.
-
point to rendered template w3c/security-questionnaire#142, by @fergald.
-
-
1 pull request closed.
-
point to rendered template w3c/security-questionnaire#142.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
1 issue received 1 new comment.
-
1 pull request opened.
-
pub rules fixes w3c/security-questionnaire#141, by @ylafon.
-
-
1 pull request merged.
-
pub rules fixes w3c/security-questionnaire#141.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
3 issues closed.
-
Privacy mitigations for identifiers w3c/security-questionnaire#79.
-
Need a "How to Use This Questionnaire" section w3c/security-questionnaire#5.
-
Contributors list? w3c/security-questionnaire#132.
-
-
8 issues received 11 new comments.
-
a question or recommendations on error-handling w3c/security-questionnaire#137 (2 comments by @pes10k)
-
Add a section for preventing behaviours that are abusive toward users w3c/security-questionnaire#106 (2 comments by @hober)
-
Explain how groups should address issues raised by the questionnaire in their specs w3c/security-questionnaire#88 (1 comment by @hober)
-
The current questionnaire is very browser-centric w3c/security-questionnaire#116 (1 comment by @hober)
-
-
3 pull requests opened.
-
draft of error handling question, fixes #137 w3c/security-questionnaire#140, by @pes10k.
-
Draft of error handling question, fixes #137 w3c/security-questionnaire#139, by @pes10k.
-
New question on hidden metadata. w3c/security-questionnaire#138, by @hober.
-
-
1 pull request merged.
-
Add an acknowledgements section. w3c/security-questionnaire#134.
-
-
2 pull requests closed.
-
Draft of error handling question, fixes #137 w3c/security-questionnaire#139.
-
User from user's agent, and expanding third parties w3c/security-questionnaire#94.
-
-
3 pull requests received 7 new comments.
-
User from user's agent, and expanding third parties w3c/security-questionnaire#94 (1 comment by @plinss)
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
a question or recommendations on error-handling w3c/security-questionnaire#137, by @npdoty.
-
GitHub
w3c/security-questionnaire
-
1 pull request merged.
-
draft of clarity and concision pass on sections 2.1 through 2.5 w3c/security-questionnaire#136.
-
-
1 pull request received 3 new comments.
-
draft of clarity and concision pass on sections 2.1 through 2.5 w3c/security-questionnaire#136 (3 comments by @hober, @pes10k)
-