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

WWW/2011/tracking-protection/drafts tracking-dnt.html,1.143,1.144

From: Roy Fielding via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 07 Aug 2012 08:45:13 +0000
To: public-tracking-commit@w3.org
Message-Id: <E1SyfPd-0007pL-El@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2011/tracking-protection/drafts
In directory hutz:/tmp/cvs-serv29993

Modified Files:
	tracking-dnt.html 
Log Message:
(editorial) restore consistency to indentation and mark-up

Index: tracking-dnt.html
===================================================================
RCS file: /w3ccvs/WWW/2011/tracking-protection/drafts/tracking-dnt.html,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -d -r1.143 -r1.144
--- tracking-dnt.html	7 Aug 2012 07:11:52 -0000	1.143
+++ tracking-dnt.html	7 Aug 2012 08:45:10 -0000	1.144
@@ -176,33 +176,33 @@
       </section>
 
       <section id='notation'>
-        <h3>Formal Syntax</h3>
-        <p>This specification uses Augmented Backus-Naur Form [[!ABNF]]
+        <h4>Formal Syntax</h4>
+        <p>
+          This specification uses Augmented Backus-Naur Form [[!ABNF]]
           to define network protocol syntax and WebIDL [[!WEBIDL]] for
-          defining scripting APIs.</p>
+          defining scripting APIs.
[...1051 lines suppressed...]
 
         <p>
           By storing a client-side configurable state and providing
-          functionality to learn about it later, this API might facilitate user
-          fingerprinting and tracking. User agent developers ought to consider
-          the possibility of fingerprinting during implementation and might
-          consider rate-limiting requests or using other heuristics to
-          mitigate fingerprinting risk. User agents SHOULD clear
-          stored user-granted exceptions when the user chooses to clear
-          cookies or other client-side state.
+          functionality to learn about it later, this API might facilitate
+          user fingerprinting and tracking. User agent developers ought to
+          consider the possibility of fingerprinting during implementation and
+          might consider rate-limiting requests or using other heuristics to
+          mitigate fingerprinting risk. User agents SHOULD clear stored
+          user-granted exceptions when the user chooses to clear cookies or
+          other client-side state.
         </p>
       </section>
     </section>
Received on Tuesday, 7 August 2012 08:45:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 7 August 2012 08:45:24 GMT