- From: CVS User rfieldin <cvsmail@w3.org>
- Date: Thu, 13 Mar 2014 06:52:57 +0000
- To: public-tracking-commit@w3.org
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory gil:/tmp/cvs-serv31531
Modified Files:
tracking-dnt.html
Log Message:
ISSUE-151: UA requirement to handle exceptions CLOSED by CfO, no change to ED
--- /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/13 06:44:56 1.241
+++ /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html 2014/03/13 06:52:57 1.242
@@ -1652,21 +1652,6 @@
on the indicated the top-level origin.
</p>
</div>
-
- <p class="issue" data-number="151" title="User Agent Requirement: Be able to handle an exception request">
- <b>[OPEN]</b> There is software that, in just a few lines of code,
- can spawn DNT:1 or DNT:0 headers regardless of user's will. A
- requirement on the user agent that they can handle the full
- exception mechanism will allow to discard compliance statements by
- those agents. It will
- also allow also the site to test for conformance by requiring an
- exception. In case the UA does not react on an exception request,
- the server could ignore DNT signals from that UA. It would allow
- thus testing from the horizon of the site without wild guessing;<br/>
- However, there is no practical difference between a UA that hard-wires
- 'no' to all exception requests, and a UA that does not implement the
- calls.
- </p>
</section>
</section>
Received on Thursday, 13 March 2014 06:52:58 UTC