769744 - Product and UX strategy for tabs

Status: RESOLVED WONTFIX

(Firefox :: Sync, defect)

Description

[Gregory Szorc [:gps]]

AFAICT we are currently lacking a unified story around how {tab sync, send tab to device, panorama, tab groups, reader mode, read it later, tabs from other computers} all play well together.

This is important for Sync because we need to decide how and where to store data. Once Sync has committed to a storage format, it is difficult to transition to something else without things breaking (like older Firefox releases). In other words, change needs to be carefully considered and planned out months in advance. This underscores the need for planning.

I would like Product and/or UX to articulate a vision for how all the aforementioned features should work in concert across multiple app types (desktop, Fennec, B2G, etc) so Sync (and other teams) can design the systems to easily achieve this vision.

I'm assigning to Asa because I don't know who else to assign to. If you already have such a vision, please drop a link in this bug and mark it resolved.

Comment 1

[Gregory Szorc [:gps]]

Add the about:home tabs and application/pinned tabs to the set of features in play here.

Comment 2

[Mike Connor [:mconnor]]

We're not currently planning to block on this for any other work.  If there is a significant evolution of tabs at some point we'll evolve Sync to work with the new model.

Comment 3

[Paul [pwd]]

So just to confirm, you're saying that none of the bugs blocking this bug are likely to be fixed?

Comment 4

[Asa Dotzler [:asa]]

(In reply to Paul [sabret00the] from comment #3)
> So just to confirm, you're saying that none of the bugs blocking this bug
> are likely to be fixed?

No. That is not what he's saying.

Comment 5

[Paul [pwd]]

(In reply to Asa Dotzler [:asa] from comment #4)
> (In reply to Paul [sabret00the] from comment #3)
> > So just to confirm, you're saying that none of the bugs blocking this bug
> > are likely to be fixed?
> 
> No. That is not what he's saying.

AFAIK Mozilla doesn't block on META bugs and this is for all intents and purposes a meta bug. And IIRC there was never a flag (mistakenly in the meta bug context) set for this bug to block anything. Which begs the question, what is he saying? Hence me asking for clarification.

Comment 6

[Chris Karlof [:ckarlof]]

We updated the synced tabs experience, and I'm closing out these old bugs to update the previous experience.