Closed
Bug 1129507
Opened 10 years ago
Closed 10 years ago
Honor DNT for Loop analytics
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(firefox38 fixed)
Tracking | Status | |
---|---|---|
firefox38 | --- | fixed |
People
(Reporter: abr, Assigned: abr)
Details
Attachments
(1 file, 2 obsolete files)
2.14 KB,
patch
|
mikedeboer
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•10 years ago
|
||
Untested, but this should be all it takes.
Assignee | ||
Comment 2•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8559234 -
Attachment is obsolete: true
Assignee | ||
Updated•10 years ago
|
Assignee: adam → nobody
Assignee | ||
Comment 3•10 years ago
|
||
Comment on attachment 8559237 [details] [diff] [review]
Honor DNT for Loop analytics
Mark: I'm not going to have the cycles to test that this works, and we really want to get it into the 0.13.4 release, but it's a really simple change. Can I have you run this through its paces (basically, run with DNT turned on and make sure nothing touches the google servers), and put an r+ on it?
If there's an issue with the code as-is, I'd like to hand ownership off to you or someone else on the team for fixing and landing.
Thanks!
Attachment #8559237 -
Flags: review?(standard8)
Assignee | ||
Comment 4•10 years ago
|
||
After some further digging, it appears that this is well-worn ground, and that the use of Google Analytics isn't "tracking" in the sense that DNT encompasses. Rather than attempting to summarize the nuance here, I'll point to this email thread on governance:
https://groups.google.com/forum/?hl=en&fromgroups=#!search/mozilla$20governance$20google$20analytics/mozilla.governance/9IQvIubDOXU/0tWVVlrUJOQJ
Also of relevance are Bug 697436 comment 14 and Bug 858839 comment 18.
As our usage appears to be within the bounds of existing Mozilla policy and practices, the changes proposed by this bug are unnecessary. I'm closing as WONTFIX.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 5•10 years ago
|
||
Based on input from our privacy folks, we're going to want to land this in the client as time allows. The current release would be ideal, but deferring to the next would be acceptable.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 6•10 years ago
|
||
I've now tested this across FF, Opera, Chrome & Safari - unfortunately there's a few different
ways that DNT is implemented, hence we need more than just one check. This catches all the major browsers and hopefully should catch any others we need.
Attachment #8561327 -
Flags: review?(nperriault)
Comment 7•10 years ago
|
||
Comment on attachment 8561327 [details] [diff] [review]
Honor DNT for Loop analytics.
I don't mind who reviews this, whoever is first is fine.
Attachment #8561327 -
Flags: review?(mdeboer)
Updated•10 years ago
|
Attachment #8559237 -
Attachment is obsolete: true
Attachment #8559237 -
Flags: review?(standard8)
Updated•10 years ago
|
Assignee: nobody → adam
Iteration: --- → 38.2 - 9 Feb
Points: --- → 1
Comment 8•10 years ago
|
||
Comment on attachment 8561327 [details] [diff] [review]
Honor DNT for Loop analytics.
Review of attachment 8561327 [details] [diff] [review]:
-----------------------------------------------------------------
LGTM.
Attachment #8561327 -
Flags: review?(nperriault)
Attachment #8561327 -
Flags: review?(mdeboer)
Attachment #8561327 -
Flags: review+
Comment 9•10 years ago
|
||
Target Milestone: --- → mozilla38
Comment 10•10 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Comment 11•10 years ago
|
||
In my opinion, the conditional statement for excluding GA when DNT signal is turned on should be ignored for browsers that are shipped from the factory with DNT on as it does not signal user intent. Namely IE10 should be ignored: http://en.wikipedia.org/wiki/Do_Not_Track#Internet_Explorer_10_default_setting_controversy
Updated•10 years ago
|
Flags: qe-verify-
You need to log in
before you can comment on or make changes to this bug.
Description
•