Firefox/Features/Persist Panorama Groups

Status

Team

Open issues/risks

• Including this feature without making Panorama groups load on demand will make the browser seem slow, since it's restoring groups that aren't visible
• Solving this problem might be easier if we get Panorama groups to be global, that's bug 578512.

Stage 1: Definition

1. Feature overview

When quitting Firefox with Panorama groups active, there's currently a perceived data loss, since you can close them in the wrong order, and lose your groups.

This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)

2. Users & use cases

`

3. Dependencies

`

4. Requirements

Open Firefox with multiple windows with groups in them, close one window at a time, start Firefox again — you shouldn't lose your groups, ever.

Non-goals

Note that it's important that we revisit this implementation when we later switch to a modal where windows == panorama groups. That is not currently a goal of this project, but it will later relate back to this project. Under that model, the risk is that Firefox will persist every window the user has ever created in Panorama (which for users who don't use the tab strip but instead favor separate windows, could be a very large number). So later the approach will be to only persist Panorama groups that the user has named/starred: design mockup

Stage 2: Design

5. Functional specification

`

6. User experience design

Described in the main bug, but short version: When doing actions that indicate that you are making use of Panorama (creating a new group, etc — the same as we use to determine whether to get the Panorama button), we 1) Turn on Session Restore for you, 2) Show an infobar for a few seconds to tell you that we did — in case you really wanted it off.

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

Main work in bug 656778, related bugs: bug 625016, bug 587400, bug 595601.

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes