From: Eric Wong <e@80x24.org>
To: Johannes Altmanninger <aclopte@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: Unexpected white-on-black text in QtWebEngine-based browsers
Date: Thu, 31 Dec 2020 22:48:37 +0000 [thread overview]
Message-ID: <X+5VRUXGtukANrOa@dcvr> (raw)
In-Reply-To: <20201231220649.psdyhorlwy6f66wh@gmail.com>
Johannes Altmanninger <aclopte@gmail.com> wrote:
> Hi,
>
> Sometime during the last two weeks, https://public-inbox.org/ started to be
> displayed as white text on black background.
I haven't changed anything in public-inbox.org
> This happens with Qutebrowser and Falkon, two QtWebEngine-based browsers.
> On Firefox or Chrome, the site displays black-on-white as usual.
It depends on your browsers' prefers-color-scheme setting which was
standardized <2 years ago, I think... I know Firefox supports it,
can't remember others.
I mainly use w3m, but whenever I use color browsers I find
light backgrounds painful to my eyes. (I'm used to minimal
room lighting to save electricity)
> It seems that contrib/css/216dark.css is in effect. That file is identical
> with the default CSS snippet in say https://public-inbox.org/git/_/text/color/,
> which seems to come from lib/PublicInbox/UserContent.pm.
Right, at least a subset w/o syntax highlighting.
> I dislike the stark contrast of white-on-black text so I'm using custom CSS
> now, but it would be interesting to know which behavior is intended.
Everybody has different eyes and environments, and any setting
I'd choose will make someone else unhappy. Best to use a browser
that respects your preferences, or a terminal browser.
Custom CSS works fine, especially if you can do it per-site.
Of course, some people are unhappy that the "homepage" is just a
directory listing :P I'm against centralization to the point
that I don't believe there should be *A* homepage.
next prev parent reply other threads:[~2020-12-31 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 22:06 Unexpected white-on-black text in QtWebEngine-based browsers Johannes Altmanninger
2020-12-31 22:48 ` Eric Wong [this message]
2020-12-31 23:16 ` Kyle Meyer
2021-01-01 9:08 ` Johannes Altmanninger
2021-01-01 9:02 ` Johannes Altmanninger
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X+5VRUXGtukANrOa@dcvr \
--to=e@80x24.org \
--cc=aclopte@gmail.com \
--cc=meta@public-inbox.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).