You need to
before you can comment on or make changes to this bug.
We decided that navigator.doNotTrack would return "yes/no/unspecified" in Firefox, but Safari 5.1 apparently  returns "1/0/(empty string)" to match the DNT header.
The reason we did "yes/no/unspecified" is because we wanted no value to parse as "false" in JS. This way, buggy code which does |if (navigator.doNotTack)| will fail closed. With 1/0/(unspecified), the bogus boolean check works so long as you never have people explicitly opting in to DNT; thus we were afraid that sites would rely on DNT being a boolean, rather than a tri-state, and then we'd never be able to send navigator.doNotTrack == "0".
How would you feel about changing to match Firefox's implementation?
> With 1/0/(unspecified), the bogus boolean check works
Er, that should be "With 1/0/(empty string)".
Perhaps confusingly, WebKit doesn't implement the doNotTrack property yet. Adding it is tracked by bug 73088.
In Safari, doNotTrack property is injected by closed source browser code. I have migrated your report to Apple's internal system, and will close this bug now as a non-WebKit issue. Thank you very much for letting us know!