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:54:19 +0000
To: David Singer <singer@apple.com>
Cc: Adrian Bateman <adrianba@microsoft.com>, "Matthias Schunter (Intel Corporation)" <mts-std@schunter.org>, "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Message-ID: <FB7E71C618E84836818AB218354C5E11@mozilla.com>



On Tuesday, 14 January 2014 at 19:52, David Singer wrote:

>  
> On Jan 14, 2014, at 11:25 , Marcos Caceres <mcaceres@mozilla.com (mailto:mcaceres@mozilla.com)> wrote:
>  
> >  
> >  
> > On Tuesday, 14 January 2014 at 19:21, Adrian Bateman wrote:
> >  
> > > 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.
> >  
> > Oh oh :( The other browsers have it on navigator. We really shouldn't be adding stuff to the window object as it's more or less equivalent to putting stuff into the global scope (also, it's not really related to the "window", it's a global setting of the "navigator").  
>  
> it might vary from window to window (this was one argument we heard). we certainly don’t need to insist that it cannot
>  


Ok, I'll have a read of the draft and educate myself a bit more on how it is intended to work. Please be careful not to over complicate this tho. The current model is easy enough to understand ("hey, all web sites: don't track me! period.") - but if it gets to having per-origin/resource control, etc. it's just going to confuse both authors and users :(  


--  
Marcos Caceres
Received on Tuesday, 14 January 2014 20:54:18 UTC

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