Open Bug 880884 Opened 10 years ago Updated 9 months ago

Polish the page displayed after a Firefox Reset

Categories

(Firefox :: Theme, enhancement)

Product:
Firefox
Component:
Theme
Type:
enhancement
Points:
5

Tracking

()

People

(Reporter: MattN, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [fxgrowth])

Attachments

(3 files)

Wireframe
142.08 KB, image/jpeg
Details
Redesigned Firefox Reset Page
845.58 KB, image/png
Details
Redesigned Firefox Reset Page 2/2
889.23 KB, image/png
Details 
Bug 833943 is implementing attachment 742261 [details] for the page users will see after Firefox Reset. We should improve the design to make it more appealing and polished. The widget containing the list of windows/tabs should remain.

Some more notes from dolske:
1) This page is an opportunity to engage with the user, helping to fix their
problem and show we care.
2) Do we want anything more here in terms of further troubleshooting /
SUMO links? Or just a simple page for now?

If the design also applies to about:sessionrestore, they currently share the same CSS so it would be trivial to share the styles but redesigning about:sessionrestore is not a requirement.
A link to a support article might be helpful for users who use this feature without visiting support first https://bugzilla.mozilla.org/show_bug.cgi?id=872240 This could help in the case where reset doesn't fix the problem. In this way we can suggest other things to look for (malware, hardware problems).
Attached image Wireframe — 
Interaction Design: 
• De-emphasis the dialog of tabs: we should restore all windows & tabs by default and users can open the dialog if they want to uncheck some tabs. I added the number of windows and tabs so users don't have to open the dialog if they just want to check whether we *really* restored everything.
• Need to find a link for users to click if reset Firefox doesn't fix their problems
In terms of copy, we should tell users that:

1. They successfully reset Firefox
2. What reset did: Most of their problems should be fixed
3. There's a link they can click if reset didn't fix their problems
4. We will restore their tabs

Anything I missed?
(In reply to Zhenshuo Fang (:fang) - Firefox UX Team from comment #2)
> • De-emphasis the dialog of tabs: we should restore all windows & tabs by
> default and users can open the dialog if they want to uncheck some tabs. I
> added the number of windows and tabs so users don't have to open the dialog
> if they just want to check whether we *really* restored everything.

Thanks Zhenshuo.

One of the reasons for showing the tabs is so that tab hoarders have a chance to see all of the tabs that they have open (possibly hidden from view in tab groups) and evaluate whether they still need them.  This would be useful for users who are resetting because of slow speed or high memory usage as the number of tabs open has an effect on both of those. For users resetting because features aren't working or users who have very few tabs I can understand how they wouldn't be interested in the list of tabs but what is the right balance? Dolske and I were even discussing having all tabs unchecked by default as a possibility.
(In reply to Matthew N. [:MattN] from comment #4)
> One of the reasons for showing the tabs is so that tab hoarders have a
> chance to see all of the tabs that they have open (possibly hidden from view
> in tab groups) and evaluate whether they still need them.  This would be
> useful for users who are resetting because of slow speed or high memory
> usage as the number of tabs open has an effect on both of those.

Does it? We don't load tabs until you select them and the overhead of unloaded tabs seems negligible.
(In reply to Zhenshuo Fang (:fang) - Firefox UX Team from comment #3)
> In terms of copy, we should tell users that:
> 
> 1. They successfully reset Firefox
> 2. What reset did: Most of their problems should be fixed
> 3. There's a link they can click if reset didn't fix their problems
> 4. We will restore their tabs
> 
> Anything I missed?

It's possible that users will realize that their problem isn't fixed only after restoring their tabs.
OK, here's what I'm thinking for this:

Success!

Firefox is reset and ready to go

Your add-ons are disabled, so you shouldn't be experiencing the same problems. If this didn't fix your issue, <a>learn more about what you can do.</a>

[x] Restore all windows & tabs (X windows, X tabs)

Or restore only the ones you want
(In reply to Matej Novak [:matej] from comment #7)
> OK, here's what I'm thinking for this:
> 
> Success!
> 
> Firefox is reset and ready to go
> 
> Your add-ons are disabled, so you shouldn't be experiencing the same
> problems. If this didn't fix your issue, <a>learn more about what you can
> do.</a>
> 
> [x] Restore all windows & tabs (X windows, X tabs)
> 
> Or restore only the ones you want

Your add-ons are gone? We don't migrate add-ons.
Right, got it. Maybe:

Your add-ons have been removed, so you shouldn't be experiencing the same problems.
(In reply to Matthew N. [:MattN] from comment #4)
> Thanks Zhenshuo.
> 
> One of the reasons for showing the tabs is so that tab hoarders have a
> chance to see all of the tabs that they have open (possibly hidden from view
> in tab groups) and evaluate whether they still need them.  This would be
> useful for users who are resetting because of slow speed or high memory
> usage as the number of tabs open has an effect on both of those. For users
> resetting because features aren't working or users who have very few tabs I
> can understand how they wouldn't be interested in the list of tabs but what
> is the right balance? Dolske and I were even discussing having all tabs
> unchecked by default as a possibility.

I think most of the times it's the add-ons that's causing a problem, not tabs. So for most users they should just restore all their tabs without going through the process of choosing what to restore. Also, even if it is a tab that's causing a problem, user probably don't know which one it is.

Maybe we should add it to the copy, something like "we removed all you add-ons, but having too many tabs may also make Firefox slow" so that users know why they don't want to restore all their tabs.
(In reply to Dão Gottwald [:dao] from comment #6)
> It's possible that users will realize that their problem isn't fixed only
> after restoring their tabs.

Yeah that's a good point. And a link is not very helpful either. I wonder if there is anything else the user can do at this point if reset doesn't fix the problem? If not, we should just tell the user "it's probably a Hardware problem and there's nothing more we can do" instead of a link...
(In reply to Zhenshuo Fang (:fang) - Firefox UX Team from comment #11)
> (In reply to Dão Gottwald [:dao] from comment #6)
> > It's possible that users will realize that their problem isn't fixed only
> > after restoring their tabs.
> 
> Yeah that's a good point. And a link is not very helpful either. I wonder if
> there is anything else the user can do at this point if reset doesn't fix
> the problem? If not, we should just tell the user "it's probably a Hardware
> problem and there's nothing more we can do" instead of a link...

I'm not sure that's true. It could be related to eg. hardware acceleration, which is automatically turned off in safe mode, but not by Firefox reset...
A User isn't very likely to realize that their problem has been fixed immediately after a Reset. Most problems will require a little bit of testing, meaning a user will likely close this page. There are some things we can do to help users that a reset didn't help (very few issues are hardware related except for HWA bugs):

If we detect that a user has reset 3+ times in the last 24 hours, we pop up a dialog saying "We noticed you have Reset Firefox multiples times. Are you having a problem with Firefox? Try visiting our support site if you need additional help.

After a Reset, after a few minutes have gone by, pop up a similar dialog: "We noticed you recently Reset Firefox. Was this to solve a problem? if the problem was solved, click here. If not, click here to go to support." This would also help us gauge how effect Reset is in the wild :)
Given that we don't load tabs until a user clicks on them, my preference here would be default to restoring all tabs. A design goal here is to make the option to restore as much of a no-brainer as possible -- i.e. have a pretty high bar for things we discard.

The option is still there for people to go through and select/deselect. Maybe in the future, when we can evaluate how problematic a person's tab burden is, we can change the defaults or make a recommendation on a case by case basis.

Doing the way proposed really streamlines this process for users, even if it might not catch all possible slowness remedies, and still does all the stuff that users can't really do themselves as they go (i.e., a person can deal with their lists of tabs in other ways, whereas he or she is unlikely to create a new profile, remove all old-addons, etc.)

(In reply to Dão Gottwald [:dao] from comment #5)
> (In reply to Matthew N. [:MattN] from comment #4)
> > One of the reasons for showing the tabs is so that tab hoarders have a
> > chance to see all of the tabs that they have open (possibly hidden from view
> > in tab groups) and evaluate whether they still need them.  This would be
> > useful for users who are resetting because of slow speed or high memory
> > usage as the number of tabs open has an effect on both of those.
> 
> Does it? We don't load tabs until you select them and the overhead of
> unloaded tabs seems negligible.
Please find the redesigned Restore page, below.


Mocks (Sketch file):
https://www.dropbox.com/s/ynoyra2b5q5uh39/Firefox_InContent_UI_Restore_v2.zip



Updates:


• Implementation of Fuera Sans as the primary incontent UI typeface

• Utilized Fox Iconography as a action indicator

• Updated language with conversational copy 

• Larger action items (e.g., radio buttons and restore panel)

• Lighter theme


Let me know if additional assets are needed.
No longer blocks: fxdesktopbacklog
Flags: firefox-backlog+
Whiteboard: [feature] p=0 → p=5
Whiteboard: p=5 → p=5 [fxgrowth]
Can we make a push on getting this done for when we roll out Firefox Refresh from the web?
Points: --- → 5
Flags: qe-verify?
Whiteboard: p=5 [fxgrowth] → [fxgrowth]
This just needs a bit of updating for the Firefox Refresh change.
(In reply to Madhava Enros [:madhava] from comment #19)
> This just needs a bit of updating for the Firefox Refresh change.

Mostly notably we should say "refreshed" instead of "reset."

I also caught a couple of typos. Would now be the time to mention and fix those?
(In reply to Matej Novak [:matej] from comment #20)
> I also caught a couple of typos. Would now be the time to mention and fix
> those?

If we're touching a string already for these changes then yes we can fix the typo at the same time.
(In reply to Matthew N. [:MattN] from comment #21)
> (In reply to Matej Novak [:matej] from comment #20)
> > I also caught a couple of typos. Would now be the time to mention and fix
> > those?
> 
> If we're touching a string already for these changes then yes we can fix the
> typo at the same time.

Great. These are in reference to the mocks in comment 18:

• As already mentioned, let's make it "Firefox is refreshed and ready to go."

• It should say "ones" instead of "one" in "Or restore only the ones you want"

• Now that I see it in layout, that leading "Or" is a bit odd. Can we just make it "Restore only the ones you want"? The or is implied.

• The button should be "Let's go!" — it's missing the apostrophe in the first mock, but not the second

• If possible, I'd also like to change "Your add-ons are removed…" to "Your add-ons have been removed…"

Thanks.
Severity: normal → S3

Changing qe-verify? to qe-verify+.

Flags: qe-verify? → qe-verify+
You need to log in before you can comment on or make changes to this bug.