W3C home > Mailing lists > Public > public-tracking@w3.org > January 2014

Re: doNotTrack attribute in API

From: Marcos Caceres <mcaceres@mozilla.com>
Date: Tue, 14 Jan 2014 20:30:40 +0000
To: Mike O'Neill <michael.oneill@baycloud.com>
Cc: 'Adrian Bateman' <adrianba@microsoft.com>, "'Matthias Schunter (Intel Corporation)'" <mts-std@schunter.org>, public-tracking@w3.org
Message-ID: <9DF395A44CFC451086DB49CB5F433B0C@mozilla.com>


On Tuesday, 14 January 2014 at 20:16, Mike O'Neill wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>  
> 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.
It matters for platform consistency and it matters to developers (as we need to know where to find this stuff predictively). It also matters to implementers, as we need to know where to put stuff so we can have an interoperable platform (as you can see already, we have a serious problem where we now have shipping products exposing this property in different places). Because this is now in the wild, it means it's going to be very difficult to change: as it would likely break content that is now relying on this being on the navigator object in the case of Chrome and Firefox - and on window in the case of IE11.   

If no user agent today is providing per-origin control over do not track (are there any UAs that support this or plan to support this?), then I would urge the group to leave it on the Navigator interface. Doing the more sophisticated per-origin DNT should maybe be done in a future version of the spec.  

You may also ask the TAG to weigh in about the above.

--  
Marcos Caceres  
Received on Tuesday, 14 January 2014 20:30:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:21 UTC