1259013 - Private Browsing is allowed in Child Mode

Status: NEW

(Firefox :: Private Browsing, enhancement)

Description

[Simona Badau, Desktop QA]

[Note]:
- Issue found on the Nightly try build from:
https://archive.mozilla.org/pub/firefox/try-builds/[e-mail]-68763a0d343f41ad9370f145abacf55068334806/

Mozilla/5.0 (Windows NT 6.3; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID:20160210105908

[Affected versions]:
- Nightly 47.0a1

[Affected platforms]:
- Windows 8.1

[Steps to reproduce]:
1. On Windows 8.1 create a Child Account and Log in
2. Install the Nightly try build 
3. Launch Nightly
4. Ctrl+Shift+P to enter Private Browsing.


[Expected result]:
Private browsing should not be allowed while in Child Mode.

[Actual result]:
Private Browsing is allowed. 

[Regression range]:
Not a regression.

[Additional notes]:
On Internet Explorer 11 the option to enter PB is not available in the Safety menu.

Comment 1

[Kamil Jozwiak [:kjozwiak]]

I'm assuming that "Disable InPrivate Mode" option under Microsofts Family Safety only affects IE/Edge. Chrome probably does it's own check and disables the appropriate features when it detects it's being run under a child account. We would need to incorporate something similar to bug # 1239166 and disable appropriate features when we detect that fx is being used in a child account.

From what I've seen via the Family Safety Web Portal, there's no turning off "Disable InPrivate Mode".

Results:

* [affected] Win 7 x64 - IE/Chrome block InPrivate/Incognito
* [affected] Win 8.1 x64 - IE/Chrome block InPrivate/Incognito
* [affected] Win 10 x64 - IE/Chrome block InPrivate/Incognito

Comment 2

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

[Tracking Requested - why for this release]: 
High impact issue which overrides any parental controls by allowing private browsing.

Comment 3

[Cornel Ionce [:noni] [Hubs QA]]

Any updates regarding this? 
We consider it a high impact issue for releasing the feature.

Comment 4

[Dana Keeler (she/her) (use needinfo) [:keeler]]

I think there's been a bit of miscommunication on scope here. My understanding is that the feature in question is essentially bug 1239166 (detecting if an account is in child mode and importing and trusting the Microsoft Family Safety root so that https sites work if so). There are certainly other things we can do when we detect that an account is in child mode, but that's out of scope for now. To address this bug specifically, it existed before we made the changes to import the family safety root, and it shouldn't blocking shipping that feature.

Comment 5

[Gerry Chang [:gchang]]

Track this as this is a high impact issue.

Comment 6

[Sylvestre Ledru [:Sylvestre]]

as David said, it is not that important.

Comment 7

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

I think this is a valid bug and a good kind of feature parity with other browsers that we can aim for in Nightly51 or 52.

Comment 8

[Simona Badau, Desktop QA]

Considering Comment 4 and Comment 7, marking this as an enhancement.