- From: Matthias Schunter via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 03 Aug 2012 16:51:10 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts In directory hutz:/tmp/cvs-serv17130 Modified Files: tracking-dnt.html Log Message: more issue sync Index: tracking-dnt.html =================================================================== RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v retrieving revision 1.135 retrieving revision 1.136 diff -u -d -r1.135 -r1.136 --- tracking-dnt.html 3 Aug 2012 16:36:38 -0000 1.135 +++ tracking-dnt.html 3 Aug 2012 16:51:06 -0000 1.136 @@ -408,13 +408,6 @@ <p class="note">This document does not have any implied or specified behavior for the user-agent treatment of cookies when DNT is enabled. </p> - <p class="issue"><a href="http://www.w3.org/2011/tracking-protection/track/issues/111">ISSUE-111</a>: Different DNT value to signify existence of site-specific exceptions<br /> - Should the user agent send a different DNT value to a first party - site if there exist site-specific exceptions for that first party? - (e.g. DNT:2 implies <q>I have Do Not Track enabled but grant - permissions to some third parties while browsing this domain</q>) - <b>[OPEN]</b> - </p> </section> <section id='js-dom'> @@ -1284,9 +1277,8 @@ <section id='exceptions' class="option"> <h2>User-Granted Exceptions</h2> - <p class="issue"><a href="http://www.w3.org/2011/tracking-protection/track/issues/111">ISSUE-111</a>: Different DNT values to signify existence of site-specific - exceptions.</p> <section id="exceptions-overview" class="informative"> + <p class='issue'><a href="http://www.w3.org/2011/tracking-protection/track/issues/144">ISSUE-144</a>: What constraints on user agents should be imposed for user/granted exceptions. <br/> <b>[OPEN</b> </p> <h2>Overview</h2> <p>
Received on Friday, 3 August 2012 16:51:11 UTC