Bugzilla Text Color Too Light - fg/bg colors provide little contrast
Devs, powers that be, The openSUSE bugzilla is becoming very hard to read for older eyes. The foreground/background colors provide light gray colored text on a white background. There is very little contrast provided. Here is a screenshot of what I see when I use bugzilla: https://paste.opensuse.org/pastes/3c0631d5b105 In Firefox (from Tumbleweed ver. 135.0), the colors are the default and the font is the default Roboto 16. Is there something that can be done to darken the text in bugzilla to reduce eye strain? -- David C. Rankin, J.D.,P.E.
On 2025-03-01 14:15, David C. Rankin wrote:
It is not that bad here. I'll take a photo. https://paste.opensuse.org/558c64a4753d Firefox 128.7.0esr (64-bit) on Leap 15.6 I noticed this "feature" decades ago on PDFs, they would use grey instead of black, for no reason. -- Cheers / Saludos, Carlos E. R. (from 15.6 x86_64 at Telcontar)
On Saturday 2025-03-01 15:25, Carlos E. R. wrote:
David is using Courier/Courier New for whatever reason. It's a font known to be unsuitable for screen rendering in general. https://en.wikipedia.org/wiki/Courier_(typeface)#Courier_New Carlos is using what appears to be Consolas. Thirdly, there is weird rendering happening in Firefox in conjunction with Freetype, e.g. https://www.goettingen-tourismus.de/weihnachtsmarkt/ and look at the cookie banner buttons' text. https://paste.opensuse.org/pastes/7bfddd531d49 [Firefox/openSUSE] https://paste.opensuse.org/pastes/e05488a499b5 [Firefox/Windows] https://paste.opensuse.org/pastes/5cbfb688b6d6 [chromium/openSUSE]
Am 01.03.25 um 16:01 schrieb Jan Engelhardt:
hm, also a good hint. My firefox is set to "monospace" for monospaced fonts and... ==> fc-match monospace SourceCodePro-Regular.otf: "Source Code Pro" "Regular" which looks pretty OK. I don't think I did anything special to prefer that one, but maybe I installed the font manually. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
On 3/1/25 21:14, Carlos E.R. via openSUSE Factory wrote:
Can I find out the font I'm actually using?
In Firefox, right click the element in the browser -> Inspect; you'll find the CSS rules on the right; also if you click the "Show all tabs" down arrow on the far right, select "Fonts", it'll show you what font is used for that element. Regards, Ahmad Samir
On 3/1/25 8:25 AM, Carlos E. R. wrote:
That isn't that bad, I wonder why the rendering difference with mine? https://paste.opensuse.org/pastes/3c0631d5b105 There is definitely a difference in how dark the font is rendering between those two pastes. Another mystery to solve! -- David C. Rankin, J.D.,P.E.
Am 01.03.25 um 14:15 schrieb David C. Rankin:
It's not that bad for me, but...
In Firefox (from Tumbleweed ver. 135.0), the colors are the default and the font is the default Roboto 16.
my tumbleweed firefox's config has been evolved over the last 20 years, so it's probably not default at all
Is there something that can be done to darken the text in bugzilla to reduce eye strain?
You can change the skin to the "Bugzilla default" (then it looks boring, like all other bugzillas, but it is probably more readable) To do this from the default openSUSE skin, you hover over your email address at the top of the window, which then opens a drop down menu (I hate this...) where you select preferences. Pretty down the list, there is "Bugzilla's general appearance (skin)", select "Classic", "submit" and voila - even the dreaded dropdown menu is gone and the colors are much better readable. At least in my setup. I'd always choose usability over looks. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
On 3/1/25 9:04 AM, Stefan Seyfried via openSUSE Factory wrote:
Will give this a go and also check what monospace is resolving to. It should be resolving to DejaVu Sans Mono, but it says "Consolas" ?? 19:59 wizard:~/dev/src-c/tmp/tst> fc-match monospace consola.ttf: "Consolas" "Regular" But in Firefox Settings Fonts -> Advanced it has: Monospace: DejaVu Sans Mono I'll play with the font and then the bugzilla skin and see if we can't make this better. -- David C. Rankin, J.D.,P.E.
On 2025-03-01 16:52, David C. Rankin wrote:
cer@Telcontar:~> fc-match monospace SourceCodePro-Regular.otf: "Source Code Pro" "Regular" cer@Telcontar:~>
But in Firefox Settings Fonts -> Advanced it has:
Monospace: DejaVu Sans Mono
monospace. (for latin).
I'll play with the font and then the bugzilla skin and see if we can't make this better.
-- Cheers / Saludos, Carlos E. R. (from 15.6 x86_64 at Telcontar)
David C. Rankin composed on 2025-03-01 07:15 (UTC-0600):
Devs, powers that be,
Here is a screenshot of what I see when I use bugzilla:
In Firefox (from Tumbleweed ver. 135.0), the colors are the default and the font is the default Roboto 16.
Is there something that can be done to darken the text in bugzilla to reduce eye strain?
I sent a reply directly to David, but as when I've done that in the past, I've seen no form of acks, I'm sending this abbreviated response to the list. That reply included an archive attachment, the content of which was from my primary profile's chrome directory. All files in the chrome directory of a Mozilla project browser's profile directory, except for userChrome.css and userContent.css, are inert, unless the file userContent.css exists containing one line for each other .css file in the following form: @import url("opensusebugz.css"); Furthermore, changes made within the profile's chrome directory are of no effect without restarting the browser, unless that's been changed without my knowledge. Tools exist that make website CSS compensations less burdensome, but I've not tried any of them (that I can remember), since I started doing as I do years before any of them existed. The painstaking method I use requires use of a browser's DOM inspector or equivalent tool, and is no fun, so I don't do it often any more. It may be that one could get by on bugzilla.opensuse.org by doing no more than creating chrome/userContent.css containing only the following (or adding it if file already exists): @-moz-document domain(bugzilla.opensuse.org) { #bugzilla-body, .bz_Enhancement td.bz_product_column, .bz_Enhancement td.bz_component_column, .bz_Major td.bz_product_column, .bz_Major td.bz_component_column, .bz_Minor td.bz_product_column, .bz_Minor td.bz_component_column, .bz_Critical td.bz_product_column, .bz_Critical td.bz_component_column, .bz_bugitem td.bz_Critical:last-child, .bz_bugitem td.bz_Major:last-child {color: #000 !important; } input, select, textarea {color: black !important; background-color: white !important; } } as a starting point good enough to get by with. The @import method I use cuts individual files down to a manageable size. "black" and "#000" and "#000000" are all equivalents meaning black in CSS. Screenshot of David's bug using browser profile with above CSS active is here: https://paste.opensuse.org/168bdee036a5 Computed font-family used there is "monospace", size 19px.
fc-match monospace DroidSansMono.ttf: "Droid Sans Mono" "Regular"
-- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
participants (8)
-
Ahmad Samir -
Carlos E. R. -
Carlos E.R. -
David C. Rankin -
Felix Miata -
J Leslie Turriff -
Jan Engelhardt -
Stefan Seyfried