Closed
Bug 530832
Opened 15 years ago
Closed 15 years ago
change layout for Merge/wipe/wipe screen in sign-in
Categories
(Firefox :: Sync, defect, P1)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
1.0 beta3
People
(Reporter: mconnor, Assigned: mconnor)
Details
Attachments
(1 file)
72.86 KB,
image/png
|
Details |
Notes from UI review: * Make the default (merge) bigger and the other two smaller? * We need better labels for the buttons. * For Option 2 (wipe local), show what local data will be deleted * For Option 3, there isn't too much we can do since we don't have a server API that shows how much data is in the server etc. But show them the names of the other machines at least. * We also need some way to tell users that they are making a choice for just one time for setup, and after that the regular behavior is to merge.
Assignee | ||
Comment 1•15 years ago
|
||
* What do you want to happen to this computer - This computer's fate is about to be decided. (instead of what do you want weave to do?)
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → mconnor
Flags: blocking-weave1.0+
Priority: -- → P1
Target Milestone: --- → 1.0 beta3
Assignee | ||
Comment 2•15 years ago
|
||
Assignee | ||
Comment 3•15 years ago
|
||
Spinning off the "more details" bits to bug 531205 http://hg.mozilla.org/labs/weave/rev/b4462709c2db
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 4•15 years ago
|
||
I propose to add diff --git a/source/chrome/skin/fx-prefs.css b/source/chrome/skin/fx-prefs.css --- a/source/chrome/skin/fx-prefs.css +++ b/source/chrome/skin/fx-prefs.css @@ -47,18 +47,18 @@ .mergeChoiceButton[selected="true"] { background-color: #888888; border-color: black !important; } .mergeChoiceButtonBox { padding: 0.5em; - max-width: 425px; + max-width: 57ch; } .mergeChoiceBFBox { - max-width: 555px; + max-width: 53ch; } .mergeChoiceImage { padding: 0.5em; } to avoid a losing of a butttons due they not fit to window width
Updated•6 years ago
|
Component: Firefox Sync: UI → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•