Closed Bug 1192314 Opened 9 years ago Closed 9 years ago

Datachoices infobar showing up on startup if upload is disabled and not shown before

Categories

(Toolkit :: Telemetry, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox42 --- affected

People

(Reporter: gfritzsche, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [unifiedTelemetry])

(In reply to Stuart Philp :sphilp from bug 1188954, comment #8)
> Okay, retested with these prefs and can confirm they are set correctly.
> 
> One issue:
> - create a new profile
> - set datareporting.policy.dataSubmissionEnabled to false 
> - restart before 60 seconds
> 
> Expected:
> - The data choices bar displays after 10 seconds
> 
> Actual:
> - The data choices bar displays after 60 seconds
> 
> If you leave datareporting.policy.dataSubmissionEnabled set to true, the bar
> does show up after 10 seconds, so this pref seems to not hit/support the 10
> second case.

This might already be fixed by bug 1191336.
Summary: Datachoices infobar showing up on startup if upload is disabled → Datachoices infobar showing up on startup if upload is disabled and not shown before
(In reply to Georg Fritzsche [:gfritzsche] from comment #0)
> This might already be fixed by bug 1191336.
Flags: needinfo?(gfritzsche)
Blocks: 1122482
No longer blocks: 1120356
Flags: needinfo?(gfritzsche)
(In reply to Georg Fritzsche [:gfritzsche] from comment #1)
> (In reply to Georg Fritzsche [:gfritzsche] from comment #0)
> > This might already be fixed by bug 1191336.
Flags: needinfo?(gfritzsche)
Blocks: 1201022
No longer blocks: 1122482
Not urgently needed, clearing needinfo for now.
Flags: needinfo?(gfritzsche)
I can still confirm this. However, if i disable FHR (datareporting.healthreport.service.enabled) we get the expected behavior.
So, this is FHR triggering the bar somehow - with FHR being obsoleted on switching over to UT there is nothing left to do here.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.