1810642 - Automatically open sent tabs

Status: NEW

(Fenix :: Accounts and Sync, enhancement)

Description

[Jonathan Almeida [:jonalmeida]]

From github: https://github.com/mozilla-mobile/fenix/issues/12294.

What is the user problem or growth opportunity you want to see solved?

Tabs sent to the device should be automatically opened in the tab list rather than popping up a notification which you then have to interact with. The current behaviour runs counter to how the desktop version works where tabs are added automatically.

How do you know that this problem exists today? Why is this important?

It's important for ease of use. As #11805 notes it can be annoying when you've sent a lot of tabs and have to click through them all to open them. However, where that bug could be solved by making a single notification for all sent tabs, what I am proposing does away with the unnecessary user interaction. After all you already knowingly sent Fenix the tabs.

Who will benefit from it?

People that regularly send tabs between devices. It also would have an additional effect of working between the various release channels as currently the notification opens in the default browser which may not be the browser you intended the tab to be sent to.

Related use cases

• https://github.com/mozilla-mobile/fenix/issues/11152

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 2

[Calum]

I was surprised to find that the expected behaviour does not match desktop Firefox and can clearly see problems:

• Non-obvious that user is required to click the notification to open it vs finding it already open in Firefox
• Multiple tabs require too much interaction with the notifications
• Too easy to accidentality dismiss or lose the notification thus break user workflow.

Comment 6

[Lina Butler [:lina]]

(Adding the dataloss keyword from bug 1858102).

There's a variation of this bug where (1) Fenix doesn't receive the push message telling it that a tab is available, (2) the user syncs manually, or Fenix eventually polls FxA to pick up missed tabs, and then (3) Fenix shows the notification. The notification is easy to miss, because the user isn't expecting it—and because we wait to open the tab until the user taps on the notification, the user never sees the sent tab.