Implement flows for signed-out and single-device users in context menus
Categories
(Firefox :: Sync, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox152 | --- | fixed |
People
(Reporter: bytesized, Assigned: bytesized)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxsync-])
Attachments
(3 files, 3 obsolete files)
From Jira:
Work is complete when the following is true:
- “send to mobile” is visible when the user is signed out, signed in with sync disabled, or only has a single device connected
- Signed out users
- opens a new tab to a sign-in/sign-up page with tracking data when “send to mobile” is clicked
- call
promiseConnectAccountURI()(example usage) with “send-tab-link-context-menu” as the entry point to open a new tab with the sign-in page- Signed in users with sync disabled
- reveals a submenu item with an “Enable sync to send a tab” item which opens
about:settings#syncwhen “send to mobile” is clicked- Single-device users
- displays two menu items divided by a separator when “send to mobile” is clicked as below
- Connect your phone
- Menu Separator
- Don’t see your device?
- when “Connect your phone” is clicked call
promisePairingURI()(example usage) with “send-tab-link-context-menu” as the entry point to open a new tab with pairing instructions- when “Don’t see your device?” is clicked a new tab is opened with a localized SUMO article of Send Tab from Firefox desktop to other devices | Firefox Help.
| Assignee | ||
Comment 1•27 days ago
|
||
Updated•23 days ago
|
| Assignee | ||
Comment 2•23 days ago
|
||
| Assignee | ||
Comment 3•20 days ago
|
||
Updated•17 days ago
|
Comment 4•16 days ago
|
||
Ready to go (this is me testing linkage, disregard).
Backed out for causing bc failures @ browser_contextmenu_sendpage.js
Comment 10•15 days ago
|
||
Comment 11•15 days ago
|
||
Backed out for causing bc failures @browser_contextmenu.js
| Assignee | ||
Updated•15 days ago
|
Comment 12•9 days ago
|
||
Comment 13•9 days ago
|
||
| Assignee | ||
Updated•9 days ago
|
Comment 15•8 days ago
|
||
Comment 16•8 days ago
|
||
Comment 17•8 days ago
•
|
||
Backed out for causing bc failures @ browser_sendtab_toolbarbutton.js
| Assignee | ||
Updated•8 days ago
|
Comment 18•7 days ago
|
||
Comment 19•6 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/b6d5ef39ce52
https://hg.mozilla.org/mozilla-central/rev/fd215fd62c4a
https://hg.mozilla.org/mozilla-central/rev/9757e2d0258a
| Assignee | ||
Comment 20•6 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D294847
Updated•6 days ago
|
| Assignee | ||
Comment 21•6 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D295722
Updated•6 days ago
|
Comment 22•6 days ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: Product says target for this feature is 151.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: yes
- Steps to reproduce for manual QE testing: Add "Send tab" button to toolbar (it looks like a phone with an arrow on the right side pointing to it). Navigate to an online page such as wikipedia. Click toolbar button. Check that "Sign in to send tabs" takes you to a sign in page at
https://accounts.firefox.com.
Sign in to a Firefox account. Ensure that no other devices are connected to the account. Click the toolbar button. Check that that "Connect phone" takes you to a URL beginning with https://accounts.firefox.com/pair. Check that "Don't see your device?" takes you to the localized version of https://support.mozilla.org/en-US/kb/send-tab-firefox-desktop-other-devices?redirectslug=send-tab-firefox-desktop-mobile&redirectlocale=en-US#w_i-dont-see-my-device-listed.
Disable sync by clicking "Manage Sync", then "Disconnect". Click the toolbar icon. Check that clicking “Enable sync to send a tab” opens a new tab to about:settings#sync.
Re-enable sync by going to about:settings#sync and clicking "Turn on syncing". Go to about:profiles and make a new profile. Sign in to Firefox with the same account used before. Navigate to an online page such as wikipedia. Click the toolbar icon. Send the tab to the first profile. Click on the notification to accept the tab being sent. Check that the tab is opened in the first profile.
All checks above should be repeated for these menus:
- Right click on the background of the page and go to "Send to Mobile"/"Send to Device".
- Right click on a link in the page and go to "Send Link to Mobile"/"Send link to Device".
- Right click on a tab and go to "Send to Mobile"/"Send to Device".
- Risk associated with taking this patch: medium
- Explanation of risk level: Two small features are basically being added here. But testing suggests that they work and it seems unlikely that they fail in a way that affects anything other than the new functionality.
- String changes made/needed?: Yes. D294847 contains a fluent migration of 3 strings and the addition of
main-context-menu-send-to-mobile-sign-in. D295722 removes strings that are no longer needed. - Is Android affected?: no
| Assignee | ||
Comment 23•6 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D296483
Comment 24•5 days ago
|
||
(In reply to Phabricator Automation from comment #22)
- String changes made/needed?: Yes. D294847 contains a fluent migration of 3 strings and the addition of
main-context-menu-send-to-mobile-sign-in. D295722 removes strings that are no longer needed.
The patch introduces 4 strings though, so 1 will remain untranslated. Similar to bug 2025884, this doesn't feel like something we should uplift to beta when we're only 4 days away from RC cut-off.
Comment 25•5 days ago
|
||
:bytesized, this is medium risk, and as mentioned in Comment 24 it also contains strings.
This is not suitable for uplift, but adding a need-info before rejecting in case there is some context missing?
I see it mentioned that Product wants to target 151, but this is not suitable given the risk and strings.
Updated•3 days ago
|
Updated•3 days ago
|
Updated•3 days ago
|
Updated•3 days ago
|
Description
•