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


From: Justin Lebar <jlebar@mozilla.com>
Date: Wed, 11 Apr 2012 11:54:37 -0400
Message-ID: <CAFWcpZ6DLDsjZ=hj1inp3+QcD+zp80XassA7CahJMQb5DQWfQQ@mail.gmail.com>
To: public-tracking@w3.org
Section 4.3.2 of the Do Not Track spec says:

"When a tracking preference is enabled, the doNotTrack attribute must
have a string value that is the same as the DNT-field-value defined in
section 4.2 DNT Header Field for HTTP Requests. If a tracking
preference is not enabled, the value is null."

This does not match our implementation in Firefox.  Instead, we return
"yes", "no", or "unspecified".

We did this so that if a web developer writes the following buggy code:

  if (navigator.doNotTrack) {
    // don't track them
  else {
    // track them

it will always fall into the "do not track" branch.  Presumably the
developer would notice this and fix their code.  (Or not, and they
don't track anybody, and that's fine too.)

In contrast, if navigator.doNotTrack returned "1", "0", or null, the
if statement above would fall into the "track" branch for null but not
"1" or "0" -- this is clearly wrong.  If developers started writing
this buggy code -- and I hope I don't need to argue that they will,
because every bug that can be made is made, and many times, on the Web
-- it would then be difficult for us to start returning "0" for
doNotTrack, since that would cause incorrect behavior.  We'd be
effectively stuck with DNT as a two-state value.

The problem is, DNT has three states.  In a reasonable implementation,
all three states should have the same true-ness -- otherwise,
developers will treat it like a boolean and get incorrect behavior.

We would like the spec changed to match our implementation.

Received on Wednesday, 11 April 2012 15:55:29 UTC

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