Update the Account Manager UI to match the Preferences Tab UI
Categories
(Thunderbird :: Theme, enhancement, P1)
Tracking
(thunderbird74 fixed)
Tracking | Status | |
---|---|---|
thunderbird74 | --- | fixed |
People
(Reporter: aleca, Assigned: Paenglab)
References
Details
Attachments
(4 files, 5 obsolete files)
496.47 KB,
image/png
|
Details | |
61.79 KB,
image/png
|
Details | |
34.22 KB,
patch
|
Paenglab
:
review+
wsmwk
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
72.42 KB,
image/png
|
Details |
Now that bug 1610445, we finally have the Account Manager living in a tab.
With that said, it looks pretty ugly.
Let's update the UI to match what we did with the Preference Tab and keep everything consistent.
Some prototyping needs to happen for the sidebar in order to properly handle those submenu elements and the button at the bottom, but for the rest, we should stick to what we have in the preferences tab.
Reporter | ||
Comment 1•5 years ago
|
||
I think the easiest and immediate step we can take is to update the overall UI to match exactly what we did in the Preferences Tab.
Let's ignore for now the UX of the left sidebar, as we'll deal with it in a follow up bug.
Richard, if I'm not wrong you took care of the Preferences Tab UI, right?
Would you be able to work on this?
Assignee | ||
Comment 2•5 years ago
|
||
I was working hard on Friday for this. ;-)
Magnus, we are touching now many files in mailnews which would break SM. And future changes, for example making the dialogs subdialogs like in prefs, would break more. Wouldn't it be better when we fork the files, like we did with the editor files, to not use many #ifdef? If yes, where do you think should we move them, components/accountmanager or components/preferences?
Assignee | ||
Comment 3•5 years ago
|
||
How it would look with the patch. No fine tuning done on reorganising the UI.
Assignee | ||
Comment 4•5 years ago
|
||
Sorry forgot to qrefresh before uploading.
Again to Magnus:
Magnus, we are touching now many files in mailnews which would break SM. And future changes, for example making the dialogs subdialogs like in prefs, would break more. Wouldn't it be better when we fork the files, like we did with the editor files, to not use many #ifdef? If yes, where do you think should we move them, components/accountmanager or components/preferences?
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Fixed the Local directory field width.
Reporter | ||
Comment 7•5 years ago
|
||
Assignee | ||
Comment 8•5 years ago
|
||
(In reply to Alessandro Castellani (:aleca) from comment #7)
Comment on attachment 9125270 [details] [diff] [review]
1613758-accountManage-in-content-styles.patchReview of attachment 9125270 [details] [diff] [review]:
Thank you so much for taking care of this, this is a bit of beast.
There are a lot of visual inconsistencies in terms of spacing, font-size,
font-weight, alignments, etc, and many things don't work, like some dialogs,
and some input fields are not rendered properly.
Correct, the font sizes aren't correct. The Font sizes/weights should now be correct. The spacing of the elements too, but it looks still different because the elements aren't the same positioned, like between the title is a input field and then the groupbox. Where is one dialog that looks a bit weird, the advanced server settings. The edit identities dialog completely uses the in-content styling. They should be fixed when they are sub dialogs.
As we fine tuned the Preferences panel pretty well, we should stick to that
exact same style without variation.So, my question is, how should we approach this?
I don't think we should duplicate the CSS styling, copying those attributes
from the pref panel and add them to the classes of the account settings.
I think we should update these class names to match what we're using in the
preferences panel, in order to prevent code duplication.What do you think?
I think the actual patch is good for landing to get the same styling as the prefs. With follow-up bug we can implement the sub dialogs (I have already a patch with the simplest dialogs) and further improvements of the remaining thing, like rearranging elements.
Also, do you want to split the patch to deal with a general style, and then
tackle each panel individually in order to land this progressively and leave
this bug open?
We could use this bug for the initial landing and then use follow-up bugs. This could be better for the history.
::: mail/themes/shared/mail/accountManage.css
@@ +10,5 @@+@import url("chrome://global/skin/in-content/common.css");
+@import url("chrome://messenger/skin/preferences/preferences.css");
+
+window {
- font-size: 1.05em !important;
Yes, on Windows it looked good. But I copied now the prefs approach which use now the exact same font metrics.
Adding this attribute to the window blows up the text and makes it look
almost doubled.
I think it's a mix of HiDPI and relative values of internal sizing.
Should be fixed.
@@ +82,5 @@
+.header {
- font-size: 1.05em;
- margin-block: 16px 4px;
- padding-bottom: 0;
This should have a font-weight: 600;
Fixed
@@ +181,3 @@
.dialogheader-title {
- margin-block: 0 8px;
- margin-inline-start: 6px;
This causes the titles to not be properly aligned to the left compared to
the rest of the content.
Fixed
Assignee | ||
Comment 9•5 years ago
|
||
Now the correct patch. Sorry.
Reporter | ||
Comment 10•5 years ago
•
|
||
Assignee | ||
Comment 11•5 years ago
|
||
Fixed the commit message. Didn't copied the spell error in your proposal. ;-)
Assignee | ||
Updated•5 years ago
|
Reporter | ||
Comment 12•5 years ago
|
||
Sweet, thanks.
Now we need to decide on some follow ups. The most obvious I can think of are:
- Fix dialogs UI.
- Improve elements (labels, inputs, checkboxes, etc) alignment.
- Improve sidebar UI.
- Improve Account Actions button UI.
Anything I'm missing?
Later on, after I finally manage to finish bug 1573678, we could implement a search field also in here.
Assignee | ||
Comment 13•5 years ago
|
||
I think, that's it. A main problem is, that it isn't one page, it uses a iframe and loads different pages in it.
Comment 14•5 years ago
|
||
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/992826d12a7e
Update the Account Manager in Tab UI to match the Preferences Tab UI. r=aleca
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 15•5 years ago
•
|
||
When testing the daily build and following the cross-link from account settings to MDN settings, I noticed that, firstly, not all subordinate dialogs have been updated yet and secondly (see Global Settings → MDN) do not scale with the zoom (the text yes, but not the pseudo window overlay size)
Reporter | ||
Comment 16•5 years ago
|
||
Thanks for the heads up, but as written in Comment 12, this is only the first step of many others to properly polish this section.
Assignee | ||
Comment 17•5 years ago
|
||
This isn't a issue of this patch. This happens with the prefs (your screenshot) too. When you set browser.zoom.full
it works as expected.
Comment 18•5 years ago
|
||
(In reply to Alessandro Castellani (:aleca) from comment #16)
Thanks for the heads up, but as written in Comment 12, this is only the first step of many others to properly polish this section.
No problem, if you're aware that the overlays doesn't scale properly yet.
(In reply to Alessandro Castellani (:aleca) from comment #12)
Later on, after I finally manage to finish bug 1573678, we could implement a search field also in here.
This would be great.
(In reply to Richard Marti (:Paenglab) from comment #17)
This isn't a issue of this patch. This happens with the prefs (your screenshot) too. When you set
browser.zoom.full
it works as expected.
Will this be enabled for standard users automatically?
Assignee | ||
Comment 19•5 years ago
|
||
Can't say now. This needs a new bug where this can be decided.
Comment 20•5 years ago
•
|
||
(In reply to Richard Marti (:Paenglab) from comment #17)
This isn't a issue of this patch. This happens with the prefs (your screenshot) too. When you set
browser.zoom.full
it works as expected.
I don't know the other effects of the option, but based on the topic here, the option should probably be set to true by default.
Maybe someone could create the spin off bug.
Comment 21•5 years ago
|
||
Comment 22•5 years ago
|
||
bugherder uplift |
Thunderbird 74.0b2:
https://hg.mozilla.org/releases/comm-beta/rev/af9061aaf712
Updated•5 years ago
|
Description
•