Compared with” Do Not Track means do not track me beyond this network interaction” or “Do Not Track means do not tell me I am being tracked” what object the property lives on is of very little importance. The TPE says window so that’s fine.


From: Adrian Bateman []
Sent: 14 January 2014 19:22
To: Matthias Schunter (Intel Corporation); (
Cc: Marcos Caceres
Subject: RE: doNotTrack attribute in API


Actually, I believe this was deliberately being moved to the window object to make it possible to tell what value was set for a particular resource. In IE11, we implemented this according to the discussions in the group. I think anything on navigator is left over from before.


From: Matthias Schunter (Intel Corporation) []
Sent: Tuesday, January 14, 2014 11:14 AM
To: (
Cc: Marcos Caceres
Subject: fyi: doNotTrack attribute in API





enclosed some technical feedback received via the public mailing list.


I appreciate the feedback and deem the changes to be non-controversial,
and I have asked Roy/David introduce corresponding edits.


Please comment if you see a need for further discussion in the WG before fixing the spec.







-----Original Message-----
From: Marcos Caceres []
Sent: Wednesday, January 08, 2014 7:59 AM
Subject: doNotTrack attribute


There seems to be some inconsistencies between the spec and browsers with regards to the `doNotTrack` IDL attribute. In the spec, it says it’s on the `window` object in some places, but in other places it says it’s on the Navigator interface. In browsers, it’s  exposed on the Navigator interface (at least in Chrome, and FF), as it should be.


Also, why is it not read only in the spec? It’s implemented as readonly in browsers - and it wouldn’t make any sense to make it writable … I’m sure it’s just an oversight :)   


Can you please correct the spec to say:


partial interface Navigator {

   readonly  attribute DOMString doNotTrack; };



Marcos Caceres