1040424 - [B2G][Settings][Firefox Accounts] Users have no method of returning to previous screen on Kids' Privacy(COPPA) page

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: FxA, defect)

Description

[Jordan de Geus(JordanD)]

Attachment: logcat_learn.txt

Description:
When users signup for a Firefox Account while selecting an age younger than 13, if the user elects to "Learn More" they will be brought to a new page/window for the FTC: Children's Online Privacy Protectioin Act(COPPA). When viewing the COPPA page, users will observe a lack of a back button to return to previous page. Users will be required to press the "home" button which returns users to the Homescreen.

Repro Steps:
1) Update a Flame to 20140717000201
2) Set device to 273mb
3) Enter Settings> Firefox Accounts
4) Enter a email address that is new> Select an age that is younger than 13 years old(Year 2002 or newer)
5) On the "Cannot Create Account" select "Learn more"
6) Observe user is taken to the FTC: COPPA page but users lack a method to return to the previous screen


Actual:
Users lack a method to return to previous menu/page when viewing the COPPA page after entering a age younger than 13 during FxA account signup
Expected:
Users have a method other than the "home" button to leave the COPPA page and return to previous menu.

Environmental Variables:
Device: Flame 2.0 (273mb)
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Repro frequency: 3/3
See attached: Logcat and Video
Logcat_learn.txt - http://youtu.be/zKDr_E9xnus

Comment 1

[Jordan de Geus(JordanD)]

This issue DOES occur on Flame 2.0 (512mb), Buri 2.0, Open C 2.0

Flame 2.0 (512mb)

Environmental Variables:
Device: Flame 2.0 
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Buri 2.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Open C 2.0

Environmental Variables:
Device: Open_C 2.0
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Actual: Upon clicking "Learn more" after failing age verification takes user to the FTC: COPPA page which users lack a method to back out

---------------------------------------------------------------------------------------------------------

Users are blocked from testing this issue on Flame 2.1, Buri 2.1, Open C 2.1 as users are unable to select an age. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1040290

Flame 2.1 (273mb)

Environmental Variables:
Device: Flame Master
Build ID: 20140717040202
Gaia: Unknown
Gecko: a74600665875
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Buri 2.1 

Environmental Variables:
Device: Buri Master
Build ID: 20140717040202
Gaia: Unknown
Gecko: a74600665875
Version: 33.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Open C 2.1

Environmental Variables:
Device: Open_C Master
Build ID: 20140717040202
Gaia: Unknown
Gecko: a74600665875
Version: 33.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

----------------------------------------------------------------------------------------------------------

Users unable to verify if this issue occurs on Flame 1.4, Flame 1.3, Buri 1.4, Buri 1.3, Open C 1.4 as these do not support Firefox Accounts

Comment 2

[Jason Smith [:jsmith]]

Kevin - I think you need to include a triage analysis here for blocking.

Comment 3

[KTucker [:KTucker][Inactive 3/4/2016]]

This is an undesired user flow but I don't think we should block on this. The user was not old enough to sign up for an account anyway so they are just returned home after given the information. I don't see this issue affecting a lot of end users.

Comment 4

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

This is by design - if the user is too young, they should not be allowed to complete the flow.

By hitting the 'home' button, they are forced out of the fxa signup flow.

Comment 5

[Jason Smith [:jsmith]]

(In reply to Jared Hirsch [:_6a68] [@6a68] from comment #4)
> This is by design - if the user is too young, they should not be allowed to
> complete the flow.

I think this isn't what the reporter concerned about. I think the reporter is concerned about the fact that they got to a point in a user flow here where they get stuck in the app with no way out other than exiting the app.

> 
> By hitting the 'home' button, they are forced out of the fxa signup flow.

Sure, but that isn't the most friendly way of exiting a flow. An app should be able to maintain it's own state via user navigation to enter and exit different workflows of the app. Shouldn't the user be able to return to the settings app without having to hit the home button here?

Comment 6

[Jason Smith [:jsmith]]

Adding UX here to provide input on comment 5.

Comment 7

[Stephany Wilkes]

Yes, this is a problem. Flagging Jacqueline who did some work on FxA. Jacqueline, please re-assign if necessary.

Comment 8

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Actually, John Gruen did the UX for FxA, but I recall discussing this flow with our PM, ni?d here.

The problem is this: if you fail the COPPA flow, you cannot try again for some period of time--this is a legal requirement, we have to kick you out of the app. What's worse, we cannot tell you why you failed the COPPA check, also a legal requirement. The current flow accomplishes this goal.

So, it doesn't make UX sense because it's a legal requirement.

Note that we are far past FC for 2.0, there is no perfect solution here, and product has signed off on the product as implemented.

Let's see if Adam wants to make changes to the approach for 2.1+.

Comment 9

[Jason Smith [:jsmith]]

(In reply to Jared Hirsch [:_6a68] [@6a68] from comment #8)
> Actually, John Gruen did the UX for FxA, but I recall discussing this flow
> with our PM, ni?d here.
> 
> The problem is this: if you fail the COPPA flow, you cannot try again for
> some period of time--this is a legal requirement, we have to kick you out of
> the app. What's worse, we cannot tell you why you failed the COPPA check,
> also a legal requirement. The current flow accomplishes this goal.

In a FxAccounts context, yes. But I'm not sure we should forcing the user out of the entire settings app here - the app itself isn't limited to FxAccounts. Why wouldn't we let the user exit out of the entire FxAccounts flow and let the user continue using the settings app?

> 
> So, it doesn't make UX sense because it's a legal requirement.

I think there's a way we can achieve the legal requirement here and have better UX here. The legal requirement seems to imply that we leave the FxAccounts flow entirely. So why can't we just exit to the settings app here?

> 
> Note that we are far past FC for 2.0, there is no perfect solution here, and
> product has signed off on the product as implemented.

Right, I'm not questioning the design decision here for 2.0. This isn't a blocking issue even if we considered this a bug.

> 
> Let's see if Adam wants to make changes to the approach for 2.1+.

Comment 10

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

(In reply to Jason Smith [:jsmith] from comment #9)
> (In reply to Jared Hirsch [:_6a68] [@6a68] from comment #8)
> > Actually, John Gruen did the UX for FxA, but I recall discussing this flow
> > with our PM, ni?d here.
> > 
> > The problem is this: if you fail the COPPA flow, you cannot try again for
> > some period of time--this is a legal requirement, we have to kick you out of
> > the app. What's worse, we cannot tell you why you failed the COPPA check,
> > also a legal requirement. The current flow accomplishes this goal.
> 
> In a FxAccounts context, yes. But I'm not sure we should forcing the user
> out of the entire settings app here - the app itself isn't limited to
> FxAccounts. Why wouldn't we let the user exit out of the entire FxAccounts
> flow and let the user continue using the settings app?

Aha, that's a very good point! I wasn't thinking of it in those terms.

Comment 11

[Adam Rogers (:arog)]

Setting this as a backlog bug - looks like an opportunity to polish the interaction a bit.  I agree with jsmith that we should likely kick the user back to settings app should their fail the COPPA check.

Comment 13

[BMO Automation]

Firefox OS is not being worked on