W3C home > Mailing lists > Public > public-tracking-commit@w3.org > August 2012

WWW/2011/tracking-protection/drafts tracking-dnt.html,1.149,1.150

From: Nick Doty via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 14 Aug 2012 01:17:14 +0000
To: public-tracking-commit@w3.org
Message-Id: <E1T15kw-0004zs-VS@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv19126/drafts

Modified Files:
	tracking-dnt.html 
Log Message:
additions per ISSUE 116

Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -d -r1.149 -r1.150
--- tracking-dnt.html	14 Aug 2012 00:51:55 -0000	1.149
+++ tracking-dnt.html	14 Aug 2012 01:17:12 -0000	1.150
@@ -422,32 +422,49 @@
         <dl class="idl" title='[NoInterfaceObject] interface NavigatorDoNotTrack'>
           <dt>readonly attribute DOMString doNotTrack</dt>
           <dd>
-            When a tracking preference is <a>enabled</a>, the
-            doNotTrack attribute MUST have a string value that is the same as
-            the <a>DNT-field-value</a> defined in
-            <a href="#dnt-header-field" class="sectionRef"></a>.
-            If a tracking preference is <a>not enabled</a>, the
-            value is <code>null</code>.
+            When a tracking preference is <a>enabled</a>, the doNotTrack
+            attribute MUST have a string value that is the same as the
+            <a>DNT-field-value</a> defined in <a href="#dnt-header-field"
+            class="sectionRef"></a> sent to the origin of the corresponding
+            top-level document. If a tracking preference is <a>not
+            enabled</a>, the value is <code>null</code>.
           </dd>
         </dl>
 
         <section id='js-implements'>
           <h4>Implements</h4>
           <div class="idl" title='Navigator implements NavigatorDoNotTrack'>
-             Objects implementing the <code>Navigator</code> interface
-             [[!NAVIGATOR]] (e.g., the <code>window.navigator</code> object)
-             MUST also implement the <code>NavigatorDoNotTrack</code></a>
-             interface.
-             An instance of <code>NavigatorDoNotTrack</code> is obtained
-             by using binding-specific casting methods on an instance of
-             <code>Navigator</code>.
+             <p>
+               Objects implementing the <code>Navigator</code> interface
+               [[!NAVIGATOR]] (e.g., the <code>window.navigator</code> object)
+               MUST also implement the <code>NavigatorDoNotTrack</code></a>
+               interface. An instance of <code>NavigatorDoNotTrack</code> is
+               obtained by using binding-specific casting methods on an
+               instance of <code>Navigator</code>.
+             </p>
+             <p>
+               The value of the <code>doNotTrack</code> attribute SHOULD be
+               considered guidance and MUST NOT be interpreted as a guarantee
+               of the value of the DNT header sent on future requests. A
+               user's tracking preference may change and may differ for
+               different origins. Servers MUST rely on the DNT header received
+               in a request even if it differs from what a script previously
+               observed in the <code>doNotTrack</code> attribute. Trackers
+               that commonly expect to receive a user-granted exception (as
+               described in <a href="#exceptions" class="sectionRef"></a>)
+               SHOULD assess the user's preference in the HTTP request loading
+               that script.
+             </p>
           </div>
         </section>
         <p class="issue" data-number="84" title="Make DNT status available to JavaScript">
           <strong>[PENDING REVIEW]</strong>
           Updated text in this section.
         </p>
-        <p class="issue" data-number="116" title="How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?"></p>
+        <p class="issue" data-number="116" title="How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?">
+          <strong>[PENDING REVIEW]</strong>
+          Updated text in this section.
+        </p>
       </section>
 
       <section id='plug-ins'>
Received on Tuesday, 14 August 2012 01:17:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 14 August 2012 01:17:16 GMT