On several places in the config dialog and otherwhere, there are listings that include one default item. We usually append "(Default)". For a number of reasons, I propose to use boldface (plus optionally a prepended icon) instead: 1. the parenthezised appendix might add up to a name that already has a parenthesized addition, 2. When changing the default, the column sizes don't adapt, so the appendix gets hidden. (Of course we also could redraw) 3. It is simply less cluttered and still visually much more obvious which one is the default. 4. Finally, it is visually also more appealing. If we go for the icon, it might be a heart or a star (often used for "favorite" which actually is a enough similar concept). But maybe someone has an even better idea? The icon should probably be appropriately tagged in order to make it compatible with screen readers. But as I'm rather sceptic if kmail is barrier-free at all, we should leave that detail for a future accessibility bugday, and shouldn't make this argument block improvements. Reproducible: Always
Created attachment 75518 [details] Screenshot: identities list This attachment demonstrates at least the first two problems with the "(default)" appendix
Git commit 3d8bf5bb6174b7793787be3c845de4245bf14b49 by Montel Laurent. Committed on 29/11/2012 at 08:13. Pushed by mlaurent into branch 'master'. Fi xBug 310823 - Use boldface (and possibly an icon) for indicating defaults FIXED-IN: 4.10 Now we autoresize column + bold default identity. I think it's enough for this bug M +5 -0 kmail/identitylistview.cpp http://commits.kde.org/kdepim/3d8bf5bb6174b7793787be3c845de4245bf14b49
Yes, for the identities list that's definitely enough - the icon was just an idea and probably unnecessary. Looks great on 4.10! However, the same applies to quite a number of lists in the config menu. I'm going to provide a patch for the other ones, as my first Junior Job. Assigning this to me.
For which config menu ? There is just 2 list which have 'by default'
I was so sure to have seen at least a third one, but can't find anymore, so I might be wrong. Outgoing accounts have been tackled on Bug #310824, so we're done here. I'm really sorry for disrupting!