Closed Bug 1077996 Opened 5 years ago Closed 5 years ago

Provide a pref to disable Loop FxA and related items (contacts, direct calling)

Categories

(Hello (Loop) :: Client, defect, P1)

defect
Points:
3

Tracking

(firefox34 verified, firefox35 verified)

VERIFIED FIXED
mozilla35
Iteration:
35.3
Tracking Status
firefox34 --- verified
firefox35 --- verified

People

(Reporter: mreavy, Assigned: MattN)

References

Details

(Whiteboard: [loop-uplift])

Attachments

(1 file)

In case we need to disable FxA/contacts/direct-calling (which really all go together), we need a single-point method of disabling it without having to deal with merges or backouts.  This would also allow us to ship Loop with accountless mode even if account mode has problems.

My preference would be to hide the FxA login (sign in/sign out) -- which would also hide contacts since contacts won't be shown if a user isn't logged in and hide the direct calling feature since direct calls are made form the contacts menu.  We'd also want to make sure we handled logging out anyone who was already logged in when they received the update.  

My thinking is this would not be a user-visible pref, and we'd only have this pref in place for the first couple of releases (for Fx34/Fx35) and remove it later (in the Fx36 timeframe).

This is something we'd want to add as soon as possible.
Priority: -- → P1
Assignee: nobody → MattN+bmo
Status: NEW → ASSIGNED
Iteration: --- → 35.3
Points: --- → 3
Flags: qe-verify+
Flags: firefox-backlog+
The pref loop.fxa.enabled set to false can disable these features. The pref requires a restart.

By logging out in initialize, I think this will cover contacts and direct calling.
Attachment #8500873 - Flags: review?(mdeboer)
Comment on attachment 8500873 [details] [diff] [review]
v.1 Allow disabling via loop.fxa.enabled

Review of attachment 8500873 [details] [diff] [review]:
-----------------------------------------------------------------

Aight, this'll do :)

Thanks!

::: browser/components/loop/test/desktop-local/panel_test.js
@@ +210,5 @@
> +          var view = TestUtils.renderIntoDocument(loop.panel.SettingsDropdown());
> +          expect(view.getDOMNode()).to.be.null;
> +      });
> +
> +

nit: one newline too many
Attachment #8500873 - Flags: review?(mdeboer) → review+
Whiteboard: [fixed-in-fx-team] → [fixed-in-fx-team][loop-uplift]
https://hg.mozilla.org/mozilla-central/rev/1ecd8bc300ba
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team][loop-uplift] → [loop-uplift]
Target Milestone: --- → mozilla35
loop.fxa.enabled hidden pref works fine.
Verified fixed 35.0a1 (2014-10-08) Win 7, Ubuntu 13.04, OS X 10.9.5
Status: RESOLVED → VERIFIED
Comment on attachment 8500873 [details] [diff] [review]
v.1 Allow disabling via loop.fxa.enabled

Approval Request Comment
Part of the staged Loop aurora second uplift set
Attachment #8500873 - Flags: approval-mozilla-aurora?
Flags: needinfo?(paul.silaghi)
Verified fixed FF 34b1 OS X 10.9.5
Flags: needinfo?(paul.silaghi)
Comment on attachment 8500873 [details] [diff] [review]
v.1 Allow disabling via loop.fxa.enabled

Already landed in aurora, approving for posterity
Attachment #8500873 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.