Closed Bug 1569662 Opened 4 years ago Closed 3 years ago

CFR: recommend sync when visiting existing bookmark


(Firefox :: Messaging System, enhancement, P1)




Firefox 71
71.3 - Sept 30 - Oct 13


(Reporter: jimthomas, Assigned: andreio)


(Depends on 1 open bug)



(1 file)

PRD (meta):

Targeting spec:

Type: Recommended Feature
Headline: Get this bookmark on your phone
Body: Take your bookmarks, passwords, history and more everywhere you're signed into Firefox.
CTA: Turn on Sync

Keywords: meta
Summary: [META] CFR: recommend sync when visiting existing bookmark → CFR: recommend sync when visiting existing bookmark

We should make sure the targeting rules apply to prevent collision with the Bookmark Panel CFR.
Currently the message targeting for Bookmark panel CFR is

!usesFirefoxSync && isFxAEnabled == true && totalBookmarksCount >= 10

This means the message is shown every time the panel opens (both when adding a bookmark or when editing a bookmark).
Should we only show it when you add a new bookmark? And if you are visiting an existing one show the awesomebar CFR?

Flags: needinfo?(jimthomas)

I'm fine with removing the bookmark panel CFR when "editing" and instead showing the awesomebar CFR.

I'd suspect that editing bookmarks from within the panel happens less frequently, especially after any immediate edits you make right when saving it, so it's likely a smaller impact (although we should watch the interaction numbers to confirm).

Flags: needinfo?(jimthomas)
Priority: -- → P2
Depends on: 1571022
Depends on: 1571023
Depends on: 1571024

Added final copy above.

Depends on: 1571374
Depends on: 1572059
Assignee: nobody → andrei.br92
Iteration: --- → 71.2 - Sept 16 - 29
Priority: P2 → P1

Now that bug 1572059 landed in GH this bug will only need to track landing the message in RS. Strings already landed.

Iteration: 71.2 - Sept 16 - 29 → 71.3 - Sept 30 - Oct 13

The message is now in RS, the message is live in 71.

Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71
You need to log in before you can comment on or make changes to this bug.