1832403 - Implement new CFR doorhanger to encourage users with FxA accounts but not syncing to begin syncing

Status: RESOLVED WONTFIX

(Firefox :: Messaging System, task, P2)

Description

[Negin Sauermann]

Scope of this bug is to land a new CFR message into tree:

+++ This bug was initially created as a clone of Bug #1828170 which was an experimenter ticket - we'd like to land this on train instead +++

The spec for the panel is here: https://www.figma.com/file/qe9yX8x51jjbt6DJYgayg2/Device-Migration?node-id=2261-19800&t=nTM9i8p1GgGtIwHS-4

The panel should:

• Hang from account icon
• Primary CTA - Takes user to the same SUMO page that bug 1828114 links to.
• Secondary CTA - Close the panel.

Ultimately, we're hoping to message users with the following characteristics:

• Existing Windows Vista/7/8 users
• Have a Fx Account
• DO NOT have sync enabled

User's should be messaged on idle, and once messaged, we should not show this message again to them.

This message should not overlap with other experiments that has “idle” target.

Comment 1

[Negin Sauermann]

Tagging you Shane in case I'm missing anything!

And just wanted to clarify since this is my first CFR, this should be as part of a message in browser/components/newtab/lib/CFRMessageProvider.jsm?

Comment 2

[Shane Hughes [:aminomancer]]

Actually I think we should probably put it in OnboardingMessageProvider - that's where recent CFR doorhangers have gone. Maybe we should ask Punam though. Punam, this CFR doorhanger will be landed on-train instead of in an experiment. Do you think it should go in CFRMessageProvider or OnboardingMessageProvider? I'm assuming the message groups should just be ["cfr"]

Comment 3

[Punam Dahiya [:pdahiya]]

Synched up with @aminomancer, initial launch of CFR will be via a Nimbus Rollout to provide flexibility of configuring message remotely for any late QA fixes and safe to mark bug as P2 in favor of bug 1828170. Thanks!

Comment 4

[Negin Sauermann]

Removing iteration until we have more information on next steps.