Submitted by Vince42 on Wed, 03/02/2016 - 17:42 Pro Licensee
Hi,
it might just be me, but italics is a "no go" in user interfaces. I already tried to fix it by extending body with text-style: normal !important; but without success. Any idea how to get rid of it?
Cheers Vince
Status:
Closed (fixed)
Comments
Hi,
Yes almost correct. This is what you need to add to the theme's extensions:
body * {
font-style: normal !important;
}
Submitted by Vince42 on Mon, 03/07/2016 - 16:54 Pro Licensee Comment #3
Awesome - my bad. :)
Aside from this "fix" you might want to consider to remove the italics in Authentic theme globally - the readability of italics / slanted is worse than that of normal fonts, especially when scaling fonts and with lower screen resolutions. Just my two cents. ;)
I will make this as a optional feature. Thanks for you advice.
Submitted by Vince42 on Wed, 05/04/2016 - 18:11 Pro Licensee Comment #5
Although this issue is already resolved, I hope that some CSS guru might give me a hint: a customer just complained, that he is no longer able to see which users are disabled (as they used to be set in italics). Is there an easy hack for displaying them in red, for example?
Submitted by andreychek on Wed, 05/04/2016 - 20:15 Comment #6
Where is it that you would like to see this particular change? That is, can you describe what screen and/or widget you're looking to apply that to?
Disabled users? Where would you like to make it be in red, which page in particular your talking about? How to navigate there?
Submitted by Vince42 on Thu, 05/12/2016 - 16:24 Pro Licensee Comment #8
Log into Webmin - Navigate to Virtualmin - Select an arbitrary virtual domain - Select "Edit users": this will show the "Mail and FTP Users" page and this is, where I need the displayed users to be displayed in red, if they are disabled. The ideal solution would be to (re)define the "disabled" CSS class so that disabled domains, users etc are always displayed in red, where they usually would have been displayed in italics. I don't know the hierarchy of CSS classes, therefore I cannot suggest the right hook for this.
Hi, Vince!
Sorry for not answering right away - I'm totally drifted away with new 18.00 release. It's blown my mind completely...
To achieve what you're asking for is simple as adding the following piece of code to Authentic Theme extensions (CSS):
form[action="change_users.cgi"] a[href*="edit_user.cgi?"]:not([href*="edit_user.cgi?new"]) > i {
color: #cb0000;
}
I'll add it to 18.00 package by default.
Submitted by Vince42 on Tue, 05/17/2016 - 09:48 Pro Licensee Comment #11
Your solution worked like charm - thank you very much!
Just my two cents regarding the theme: as already stated above italics are usually not well readable - I would recommend the colorization instead. Or you could offer the user to choose between italics and color.
You are very welcome.
To be honest, I have no hard time reading italics. :)
Why not add to extensions some code that would remove all italics completely for you and your users?
Or you think it's necessary to make an options for do it? Don't you think it's overkill and what for the extensions were created?
Submitted by Vince42 on Tue, 05/17/2016 - 10:02 Pro Licensee Comment #13
Don't get me wrong, please: I am also able to read italics as most ppl are.
The point with avoiding italics is, that there are manifold reasons why italics might not work (text browser not supporting it, chosen font not providing it) - and therefore it is rather a question of usability and user experience. At least the feedback from my customers was "thank god that the ugly text (aka italics) is finally gone".
An option might be an overkill ... If it were up to me to decide, I would remove italics by default and make clear color coding instead. For example: I noticed some information that was printed in italics, where I automatically wondered: why is this set in italics? I would implement (in v19 :P) some classes, which express the intention of emphasizing certain information (like "disabled" "warning" etc) and give those some meaningful default colors. People are visually attracted and I bet that most of them would prefer colors over italics. ;)
I did already remove all italics (which was the original intention of this issue) - and am glad to have now a visual replacement for the places, where it is needed.
There are classes already but they are not used on server-side (in Perl by modules). I could make it hacky, like I did for your previous case but this is not very right solution.
Submitted by Vince42 on Thu, 05/19/2016 - 18:06 Pro Licensee Comment #15
I totally agree ... the only good solution would be to separate functionality / data from displaying ... well, there is still hope for some future Webmin / Virtualmin / Usermin release, that all CSS classes are properly respected and easily configurable. :)