w3ctag security-questionnaire issues

w3ctag / security-questionnaire

A security/privacy review questionnaire for W3C specs

https://w3ctag.github.io/security-questionnaire/

Creative Commons Zero v1.0 Universal

25 stars 34 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

2.10 mis-spelled 'features'

#129 dwsinger closed 2 years ago
2
Add non-"fully active" document question

#128 rakina closed 3 years ago
2
Spelling: feautures

#127 jyasskin closed 3 years ago
0
Fixes typos of "features"

#126 Kangz closed 3 years ago
1
Typo in "no known security impacts" boilerplate

#125 scottaohara closed 3 years ago
2
Minor fixes

#124 bialpio closed 3 years ago
1
Minor changes to questionnaire.markdown

#123 bialpio closed 3 years ago
1
Mention (capability) negotiation?

#122 samuelweiler closed 4 months ago
3
Bring questionnaire.markdown up to date

#121 alice closed 3 years ago
1
Update to Process 2020

#120 wseltzer closed 3 years ago
0
Correct a typographical error: feautures -> features.

#119 jeremyroman closed 3 years ago
1
Fix small typos

#118 chcunningham closed 3 years ago
1
Revise 2.16 for clarity. Fixes #102.

#117 hober closed 3 years ago
2
The current questionnaire is very browser-centric

#116 atanassov closed 4 months ago
3
Revise question 2.7 for clarity.

#115 hober closed 3 years ago
0
First attempt at addressing #104.

#114 cynthia closed 3 years ago
1
Supply chains can be trusted – with evidence

#113 jwrosewell closed 3 years ago
0
Supply chains can be trusted – with evidence

#112 jwrosewell closed 3 years ago
1
W3C antitrust policy prohibits this document in its current form

#111 jwrosewell closed 3 years ago
3
point to a specific section of rfc3552

#110 samuelweiler closed 4 years ago
0
make use of spec and feature more consistant, fixes #105

#109 pes10k closed 3 years ago
2
fix build

#108 samuelweiler closed 4 years ago
0
do a toe to tip read and make a high level suggestion for what can be cut

#107 pes10k opened 4 years ago
2
Add a section for preventing behaviours that are abusive toward users

#106 hadleybeeman closed 4 months ago
3
"feature" or "specification"?

#105 samuelweiler closed 3 years ago
0
2.9 (script loading) needs wrapper text

#104 samuelweiler closed 3 years ago
1
editorial + sec/priv sections rewrite + howto rewrite

#103 samuelweiler closed 4 years ago
2
2.16 (relaxed-sop) what are the bullet items?

#102 samuelweiler closed 3 years ago
0
use automatic publishing

#101 samuelweiler opened 4 years ago
17
merge questions 2.1 and 2.8

#100 pes10k closed 2 years ago
3
New question: Does this specification allow an origin to send data to the underlying platform? Fixes #96.

#99 hober closed 3 years ago
3
Revise 2.6 for clarity.

#98 hober closed 4 years ago
0
Consider merging or retitling questions 2.1 and 2.8

#97 hober closed 2 years ago
4
Lessons from sharing URLs

#96 marcoscaceres closed 3 years ago
2
Fix the build.

#95 hober closed 4 years ago
0
User from user's agent, and expanding third parties

#94 jwrosewell closed 2 years ago
6
Rename master branch to main

#93 hober closed 3 years ago
2
Incompatible with guidance on other concerns

#92 jwrosewell closed 4 years ago
3
Revise questions 2.4 and 2.5 for clarity.

#91 hober closed 4 years ago
2
Revise questions 2.1, 2.2, and 2.3 for ease of understanding.

#90 hober closed 4 years ago
1
Strip leading whitespace, and make other small tweaks

#89 hober closed 4 years ago
0
Explain how groups should address issues raised by the questionnaire in their specs

#88 pes10k closed 4 months ago
6
Rewrite the Abstract and Introduction.

#87 hober closed 4 years ago
2
Provide custom Bikeshed boilerplate since this is a joint TAG/PING publication.

#86 hober closed 4 years ago
0
Bias – needs to encompass a fuller set of considerations

#85 jwrosewell closed 4 years ago
4
Bad (or good) behaviour by first parties

#84 jwrosewell closed 4 years ago
9
Supply chains can be trusted - expand document to consider this possibility

#83 jwrosewell closed 4 years ago
33
Revise Abstract, Introduction, and How To Use The Questionnaire sections

#82 torgo closed 4 years ago
0
Use GitHub Actions instead of Travis-CI for publishing to gh-pages.

#81 hober closed 4 years ago
3
Privacy mitigations for identifiers

#79 wseltzer closed 2 years ago
3

Previous Next