Mostly involves moving engine and first sync settings into separate Sync Options dialog.
Component: Sync → Firefox UI
QA Contact: sync → firefox
The Sync Options dialog looks like another wizard page in the mockup, but I think it makes more sense to implement it was a dialog. It's clearly modal and it will be reused for Reset Sync (yes, we reuse the wizard there right now, but that always felt weird to me).
The only problem with making this a dialog is that Reset Sync would lose the confirmation page. But we don't really have it in the wizard anymore, either (unless you count the Setup Complete page as such). Thoughts?
Created attachment 471390 [details] [diff] [review] v1 This changes the setup flow to match Alex's mockups. Some notes: * This does change strings where appropriate, but it might not have covered all. We should probably revise any outstanding strings in a separate bug. * While the size of the wizard and the styling of certain elements are changed, this isn't meant to include any significant styling changes. See bug 591122 and bug 592839 for those.
Created attachment 471537 [details] [diff] [review] v1.1 Small rev on v1: Also switch over the accesskey when relabeling the buttons (for going into the Sync Options part of the wizard).
Created attachment 471878 [details] [diff] [review] v2 Incorporate faaborg's feedback: * Rename the "Create you Firefox Sync Account" page to "Account Details" as per mockups. * Rename and move the "Server" form field as per mockups. * Check email validity when the textbox loses focus, not on every character. * Display captcha error messages inline instead of prompting an alert dialog.
Created attachment 471897 [details] [diff] [review] v2.1 One more feedback from faaborg: * Use syncBrand.shortName (Sync) instead of syncBrand.fullName (Firefox Sync) on Sync Options page.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Verified. Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100924 Firefox/4.0b7pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.