From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 8FB9B1F4B4; Thu, 31 Dec 2020 22:48:38 +0000 (UTC) Date: Thu, 31 Dec 2020 22:48:37 +0000 From: Eric Wong To: Johannes Altmanninger Cc: meta@public-inbox.org Subject: Re: Unexpected white-on-black text in QtWebEngine-based browsers Message-ID: References: <20201231220649.psdyhorlwy6f66wh@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201231220649.psdyhorlwy6f66wh@gmail.com> List-Id: Johannes Altmanninger 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.