Revamp the setup wizard according to Faaborg's mockups.

(In reply to comment #0) > Revamp the setup wizard according to Faaborg's mockups. Phillipp, could you attach the mockup?

I'm making some quick modifications and will be posting a revised version soon.

Here is i4 of the sync set up flow. This completes everything in 5 steps, and uses an automatically generated Sync key (to reduce confusion with the password, convince the user to save a copy, and ensure really good entropy for encryption).

Should this be in this component, or in Firefox::General? If this one, then I might create a tracking bug in Firefox::General that depends on this one for the purposes of getting it on the blocking radar.

We will probably land this in fx-sync first since there might be client library changes and then port to Firefox. Filed bug 590805 to track in Firefox::General.

Can the current design (Gecko/20100908 Firefox/4.0b6pre) be considered definitive/stable? There are several problems with localized builds (titles partially displayed because of the big font, horizontal scrollbars, unwanted space in a string) and I'd like to know if it's better to wait before filing new bugs.

(In reply to comment #6) > Can the current design (Gecko/20100908 Firefox/4.0b6pre) be considered > definitive/stable? No, there's still fine tuning to be done. > There are several problems with localized builds (titles partially displayed > because of the big font, horizontal scrollbars, unwanted space in a string) and > I'd like to know if it's better to wait before filing new bugs. You can pile your comments on bug 591122 or if you do file new ones, make them block that bug. Thanks!

Comment on attachment 478627 [details] Comparison between Sync Setup Wizard and Import Wizard Is there any reason why the Sync Setup Wizard looks SO MUCH different from all other built-in wizards? IMO, they should all look similar. Right now, it looks pretty much out of context, as if it still were a third-party extension with totally different people behind its design.

Oh, it's a wrong bug. Sorry...

This was done before Firefox 4, minus the styling follow-up bugs.