Closed Bug 1334430 Opened 5 years ago Closed 5 years ago

Synced tabs in hamburger menu UX is worse than in-content about:sync-tabs

Categories

(Firefox :: Sync, defect, P3)

defect

Tracking

()

RESOLVED FIXED
Firefox 55
Tracking Status
firefox54 --- wontfix
firefox55 --- fixed

People

(Reporter: djc, Assigned: eoger)

References

Details

(Keywords: ux-efficiency, Whiteboard: [sync-ui-polish])

Attachments

(1 file)

Some time ago, the History > Synced Tabs was changed to point to a side menu in the hamburger menu thing. For my uses, the UX for this is much worse than the old about:sync-tabs UX, primarily:

- The new way opens a synced tab link in my current tab, which is never what I want.
- In the new way, the menu disappears after clicking one of the links, making it very laborious to open multiple tabs from another device in my current session.

To me, the use case of "bringing a somewhat-sizable set of tabs to another device" is pretty important. The old in-content does not really facilitate this use case well, but it still does a better job than the new version.
(In reply to Dirkjan Ochtman (:djc) from comment #0)
> - The new way opens a synced tab link in my current tab, which is never what
> I want.

This has been designed to work like the other similar panels - eg, a middle-click will open in a new tab. We also see similar complaints for the sidebar, but all other sidebars work the same way.

> - In the new way, the menu disappears after clicking one of the links,
> making it very laborious to open multiple tabs from another device in my
> current session.

There is a synced tabs sidebar that you might find more useful for this purpose. We also recently landed a change to the sidebar to allow you to open all from a device with a single click.

> To me, the use case of "bringing a somewhat-sizable set of tabs to another
> device" is pretty important. The old in-content does not really facilitate
> this use case well, but it still does a better job than the new version.

I suspect this will be "wontfix", but I'll leave that up to our UX team. Ryan, what do you think?
Flags: needinfo?(rfeeley)
I spend most of my time on track pads, so no middle-click.

The sidebar is much nicer, but not very discoverable as it is. Maybe it would make sense to have History > Synced Tabs (and the hamburger menu item, as far as I'm concerned) open the sidebar?
The good news is that panels and sidebars are being redesigned for Quantum by a UX project called Quantum. I will cc: Stephen Horlander so they can take multi-select and where links open into account.
Flags: needinfo?(rfeeley)
Flags: needinfo?(eoger)
Ryan what do you think of not closing the menu when Ctrl+clicking or middle clicking an item? It's a quick and easy fix that would help.
Sure!
Flags: needinfo?(eoger)
Assignee: nobody → eoger
Status: NEW → ASSIGNED
Priority: -- → P1
Comment on attachment 8834612 [details]
Bug 1334430 - Keep the Synced Tabs panel open when not opening a tab in the current tab.

Not ready for review, another bug is blocking this.
Attachment #8834612 - Flags: review?(markh)
Comment on attachment 8834612 [details]
Bug 1334430 - Keep the Synced Tabs panel open when not opening a tab in the current tab.

https://reviewboard.mozilla.org/r/110468/#review111730

seems nice and simple, thanks! I think a comment that explains the intent would be nice though (ie, it's not particularly obvious from that patch exactly why the code exists)
Attachment #8834612 - Flags: review+
Depends on: 1337531
P3 as it's not actionable until bug 1337531 is fixed.
Assignee: eoger → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3
Whiteboard: [sync-ui-polish]
Looks like bug 1349742 fixed our blocking bug, good thing I read the Quantum Flow Newsletter religiously 
Assignee: nobody → eoger
Pushed by eoger@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2c488ee373ab
Keep the Synced Tabs panel open when not opening a tab in the current tab. r=markh
https://hg.mozilla.org/mozilla-central/rev/2c488ee373ab
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Mark 54 won't fix as it's late for Beta54.
You need to log in before you can comment on or make changes to this bug.