Closed
Bug 733522
Opened 13 years ago
Closed 12 years ago
Don't show Telemetry opt-out notification for users who have already opted in or out
Categories
(Toolkit :: Telemetry, defect)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox20 | --- | fixed |
People
(Reporter: lmandel, Assigned: theo)
References
Details
Attachments
(1 file)
2.14 KB,
patch
|
Details | Diff | Splinter Review |
Bug 725407 added a notification for Aurora/Nightly users that Telemetry is opt-out on these channels. The notification will be shown to all users. However, if a user has already opted in or out of Telemetry we will continue to respect their selection. In this case we should not show the prompt as we do not want to confuse the user.
Looks to me like the code that needs to change is in nsBrowserGlue.js.
if (telemetryNotifiedOptOut)
return;
should be
var telemetryEnabled = telemetryEnabledByDefault = Services.prefs.getBoolPref(PREF_TELEMETRY_ENABLED);
var telemetryRejected = telemetryEnabledByDefault = Services.prefs.getBoolPref(PREF_TELEMETRY_REJECTED);
var telemetryChosen = telemetryEnabled || telemetryRejected;
if (telemetryNotifiedOptOut || telemetryChosen)
return;
Comment 1•13 years ago
|
||
I think this is what you were proposing, Lawrence.
Attachment #603768 -
Flags: review?(gavin.sharp)
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Nathan Froyd (:froydnj) from comment #1)
> I think this is what you were proposing, Lawrence.
Yes it is. Thanks for the quick turnaround.
Comment 3•13 years ago
|
||
I think that if we revisit bug 699806 per my latest comment there, we won't need to worry about handling all of these cases separately, and this patch will be unnecessary.
Updated•13 years ago
|
Attachment #603768 -
Flags: review?(gavin.sharp)
Comment 4•12 years ago
|
||
tentatively assigning to Theo, regardless we need to fix this along with bug 699806, even if just in the patch there.
Assignee: nobody → theo.chevalier11
Blocks: 699806
Assignee | ||
Comment 5•12 years ago
|
||
Closing this bug since we fixed it in bug 699806 for desktop and bug 725987 for mobile.
You need to log in
before you can comment on or make changes to this bug.
Description
•