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

Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160

From: David Singer <singer@apple.com>
Date: Mon, 05 Nov 2012 16:19:46 +0100
Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Message-id: <A17AEABF-F5DE-40B6-907D-D49BCB3A152A@apple.com>
To: Matthias Schunter <mts-std@schunter.org> (Intel Corporation)

On Nov 5, 2012, at 14:56 , Matthias Schunter (Intel Corporation) <mts-std@schunter.org> wrote:

> ---------------------------------------------------------------
> ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?
> http://www.w3.org/2011/tracking-protection/track/issues/116
> Nick proposed to "The diff included below (also attached) would update the draft to move the JS doNotTrack property to window (from navigator) and remove the requestDNTStatus( ) method (which would now be redundant). "
> http://www.w3.org/2011/tracking-protection/track/actions/318
> I suggest to implement this change and close ISSUE-116

I think Nick's note does two things:

* get the APIs on the right objects (uncontroversial)
* reduces from two APIs to one

We currently have both of
a) what is the user's "general preference"?
b) what DNT signal would be sent to a given origin?

Nick proposes deleting the former; I don't have any problem with that, but we need to realize it's happening.

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Monday, 5 November 2012 15:20:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:39:13 UTC