Created attachment 8685692 [details] logcat_metrics-change.txt Description: When progressing through the FTU, the Usage Metrics Data page will allow the user to select between Basic, Enhanced, and None reporting levels. This option is disabled on Dogfood builds, and automatically configured to Enhanced. However, these options are still selectable to the user for a brief period of time the first time the page is loaded. The user is able to change this setting before the option becomes greyed out and unselectable, and then the user is unable to change it back. The timing is very specific to do this, but a determined (or possibly clumsy) user is able to change this setting. Note: If the user doesn't get the timing right, they can restart the device before completing the FTU and attempt again. Repro Steps: 1) Update a Aries to 20151105134116 2) Progress through the FTU, pausing at the Contact Import screen. 3) Press the Next button, and immediately press either the 'None" or "Basic" radio buttons to change the metrics setting. Actual: The user is able to change the metrics setting before it is made unselectable on a Dogfood build.. Expected: The user is not able to modify the metrics setting on a dogfood build. Environmental Variables: Device: Aries 2.6 Build ID: 20151105134116 Gaia: c3be747b993f0c70e7b93a709ef691383c88fc01 Gecko: 61dcc13d0848230382d5c85cdcf6721a05ee37c6 Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56 Version: 45.0a1 (2.6) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0 Repro frequency: 2/5 See attached: Logcat, Video (URL)
This issue DOES occur on the latest Aries 2.5 Dogfood build. The user is able to change the metrics setting before it is made unselectable on a Dogfood build. Environmental Variables: Device: Aries 2.5 BuildID: 20151110170210 Gaia: 07baf613699fa6225359c7f04825c5caeb71d424 Gecko: 361f2673aadc988918a551b45ecef4cce58edf1e Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56 Version: 44.0a2 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
[Blocking Requested - why for this release]: This should be fixed since the user can get around sending their data on a dogfood build even though it is kind of a tester bug. Nominating 2.5? Can you take a look at this please Gerry?
blocking-b2g: --- → 2.5?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(gchang)
1. I would like to confirm if not allowing user to change the data setting on dogfood devices is the default option. 2. Since the recreate rate is not high and user needs to do this intentionally, NI developer to determine if this needs to be fixed in 2.5.
Per above comment, NI developer.
Hi Gerry, For dogfooding, the user should not be allowed to change the option. So, yes, this is a bug if Martin is saying it can be changed. My .02 is that it's not a blocker as you mention, the user needs to read, understand and then try to do something. If someone really wants to try and get around this, there are other ways, besides this. Incidentally, I can't repro this on Flame. Thanks, -tamara
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.