From: Luis Felipe via Bug-mumi via "Bug reports for GNU Guix Mumi." <bug-mumi@gnu.org>
To: bug-guix@gnu.org
Subject: bug#71443: [mumi] Some HTML elements don't respond to preferred color scheme when JS is disabled
Date: Sat, 8 Jun 2024 19:54:43 +0000 [thread overview]
Message-ID: <4e455dd4-a68e-52ff-5325-a12f4b5466f7@zoho.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1644 bytes --]
Package: mumi
Hi,
When using a web browser with JavaScript disabled, the body element and
the text input of class ".tokenInput" don't use the correct color theme.
This doesn't affect people who use light themes, but it does affect
people who use dark themes because it introduces contrast issues (light
text on light backgrounds).
STEPS TO REPRODUCE
1. Launch IceCat web browser
2. Enable user defined color scheme preferences by disabling
Application menu → IceCat Settings → Resist Fingerprinting
3. Set your color scheme preferences to Dark in: Application menu →
Settings → Language and Appearance → Website appearance
4. Disable JavaScript in: Application menu → IceCat Settings → Disable
Javascript
5. Visit https://issues.guix.gnu.org/
6. Press Ctrl+F5 to avoid using cached resources
EXPECTED RESULT
The website uses the dark color scheme.
UNEXPECTED RESULT
The HTML body element and the text input of class ".tokenInput" don't
use the dark color scheme, while the rest of the elements do use it.
ADDITIONAL INFORMATION
There seems to be something wrong with the functionality of the
"--background-color" variable. While it seems to have appropriate values
assigned to it for every color scheme case (prefers light, prefers dark,
and no preference), the dark color value is not being used when needed.
I still don't know why.
WORKAROUND
Assigning the value of "var(--nav-background-color)" to the
"background-color" property of the affected elements solves the issue.
--
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next reply other threads:[~2024-06-09 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 19:54 Luis Felipe via Bug-mumi via Bug reports for GNU Guix Mumi. [this message]
2024-06-08 23:19 ` bug#71443: [PATCH] assets: Make body and .tokenInput color scheme aware in non JS browsers sirgazil--- via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-06-09 13:30 ` bug#71443: [PATCH 0/1] Set --background-color variable in dark theme Arun Isaac
2024-06-09 13:30 ` bug#71443: [PATCH 1/1] assets: " Arun Isaac
2024-06-09 13:32 ` bug#71443: [mumi] Some HTML elements don't respond to preferred color scheme when JS is disabled Arun Isaac
2024-06-09 22:35 ` Luis Felipe via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-06-10 11:44 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://issues.guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e455dd4-a68e-52ff-5325-a12f4b5466f7@zoho.com \
--to=bug-mumi@gnu.org \
--cc=bug-guix@gnu.org \
--cc=sirgazil@zoho.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).