- From: Karl Dubost <karld@opera.com>
- Date: Mon, 14 Nov 2011 15:24:37 -0500
- To: Shane Wiley <wileys@yahoo-inc.com>
- Cc: Andy Zeigler <andyzei@microsoft.com>, "Tracking Protection Working Group WG (public-tracking@w3.org)" <public-tracking@w3.org>
Le 13 nov. 2011 à 17:20, Shane Wiley a écrit : > I believe there are many benefits to a browser managed list of exceptions: > · User able to retract exceptions outside of direct contact with a specific 3rd party > · User able to see all of the exceptions granted to date How do you make the distinction with the changing role of some domain names (once 1st party, once 3rd party)? > · Exception list could be used to help manage 1st party/3rd party granted exceptions (for example, PublisherXYZ requests an exception for their site and the 4 3rd parties they work with in exchange for free content. The exception list would be able to tie the exception for that 3rd party only in the context of this 1st party. > · Enables external audits (remove entry from list – look at header response code for correct behavior) What would be the UI of this? Or the sequence of User Experience for managing it? Could you send a draft of how you would see it as a *user*? -- Karl Dubost - http://dev.opera.com/ Developer Relations & Tools, Opera Software
Received on Monday, 14 November 2011 20:25:15 UTC