W3C home > Mailing lists > Public > public-tracking@w3.org > July 2017

RE: editor's note on the navigator property

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Mon, 17 Jul 2017 16:10:23 +0100
To: "'David Singer'" <singer@mac.com>, <public-tracking@w3.org>
Message-ID: <2a1f01d2ff0e$d054d050$70fe70f0$@baycloud.com>

If the code that needed to check was in a "target" i.e. sub-resource browsing context, the confirm would be useless anyway (only the browsing context that requested the exception could meaningfully call confirm)

The only way to then get the DNT value would be then to bounce an XHR off the server - yuck.

I agree we should just keep it.

I think Roy recognised that in the last call anyway.


-----Original Message-----
From: David Singer [mailto:singer@mac.com] 
Sent: 17 July 2017 14:43
To: public-tracking@w3.org (public-tracking@w3.org) <public-tracking@w3.org>
Subject: editor's note on the navigator property

I don’t understand this editor’s note in the draft:

"the doNotTrack property which now appears to be useless”

Why is it useless?  It computes the header that would be sent to the domain of the requestor. The result is impacted by (at least):

a) the user’s general preference
b) whether there is a web-wide exception that I have requested and been granted (ok, this is something I both should know and could verify in other ways)
c) whether I am embedded in a site that has requested a site-specific exception that includes me (OK, I could try to confirm the duplet formed by the top-level browsing context and me, and confirm that exception, but what a hassle)

There are (at least) these three to check, and I don’t believe a script has any other way to get (a).

What am I missing?

Dave Singer

Received on Monday, 17 July 2017 15:11:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:36 UTC