Added TAG security and privacy questionnaire #550
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@xhwang-chromium @joeyparrish I will need your help to complete this. Please have a look, you're welcome to add commits to this branch to add any details. |
|
@xhwang-chromium @joeyparrish @gregwfreedman I have added some more detail, please review. Please also add information where there are still TODO items. |
chrisn
force-pushed
the
security-privacy
branch
from
17d664d to
e6f54de
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an initial draft set of answers to the W3C's Security and Privacy self review.
See https://www.w3.org/Guide/documentreview/ for more details on horizontal review.
This is focused on the changes introduced in EME v2.
I've added answers from #473 (comment), covering handling of hardware context reset.
Still to do: