Re: fyi: doNotTrack attribute in API

I imagine at some point the spec will need a more extensive review of the API. I found those by just quickly scanning the spec so I suspect there might be other issues. Please let me know when the spec is a bit more stable so I can do a more detailed review.  

Also, it would be great if the spec was on github and/or at least had a bug tracker - it would make it easier for implementers and reviewers to help advance the spec.   

Thanks!   

--  
Marcos Caceres


On Tuesday, 14 January 2014 at 19:14, Matthias Schunter (Intel Corporation) wrote:

> Hi TPWG,
>  
>  
> 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.  
>  
>  
> Regards,
> Matthias
>  
>  
> -----Original Message-----
> From: Marcos Caceres [mailto:mcaceres@mozilla.com]  
> Sent: Wednesday, January 08, 2014 7:59 AM
> To: public-tracking-comments@w3.org
> 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
>  
>  
>

Received on Tuesday, 14 January 2014 19:20:45 UTC