Skip to content
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

Triage privacy issues #348

Closed
marcoscaceres opened this issue Apr 2, 2015 · 5 comments
Closed

Triage privacy issues #348

marcoscaceres opened this issue Apr 2, 2015 · 5 comments
Assignees

Comments

@marcoscaceres
Copy link
Member

Lots of feedback here...
https://lists.w3.org/Archives/Public/public-privacy/2015JanMar/0118.html

cc @npdoty, who we need to work with to address the above...

@npdoty
Copy link

npdoty commented Apr 2, 2015

The more formal write-up that I sent to webapps may be better organized and easier to follow for identifying issues:
https://lists.w3.org/Archives/Public/public-privacy/2015JanMar/0117.html

@marcoscaceres
Copy link
Member Author

That's great! thank you. That makes things much easier.

@mounirlamouri mounirlamouri added P1 and removed P3 labels Aug 25, 2015
@mounirlamouri mounirlamouri self-assigned this Aug 25, 2015
@mounirlamouri
Copy link
Member

persistent state: #399
cross origin persistent state: #400
control over native ui: #401 #402

@npdoty, please, let me know if I missed something.

@marcoscaceres
Copy link
Member Author

@mounirlamouri did the triage. We didn't hear back from @npdoty, so assuming it's all good.

@npdoty
Copy link

npdoty commented Mar 22, 2016

Sorry for not following up explicitly. Yes, this separation into GitHub issues seems to cover the privacy/security issues raised in our comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants