All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong+korg@djwong.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: lore.kernel.org upgrade: Sep 1, 2021
Date: Tue, 31 Aug 2021 18:23:10 -0700	[thread overview]
Message-ID: <20210901012310.GL4159675@sweaglesw.org> (raw)
In-Reply-To: <20210830164626.tq5emfrht4o46x33@nitro.local>

On Mon, Aug 30, 2021 at 12:46:26PM -0400, Konstantin Ryabitsev wrote:
> Hi, all:
> 
> My tests of the new lore.kernel.org service (currently running on
> x-lore.kernel.org) are looking good, so I will be putting that into production
> on Wednesday, September 1, 2021.

Any chance I could persuade you to remove the color changes in the CSS
stylesheet?  The text colors on the new x-lore appear washed out to me
due to "color: #333;", which makes it harder to read.

I can hack around all that stylistic choice by adding more rules to my
bespoke browser extension that makes the web readable again for my old
eyes, but I'd prefer the current lore's stylesheet, which uses the user
agent's preferences.

Something like this, perhaps?

--D

css: use the user agent's text colors

Despite the comment for the color scheme claiming that "...bright colors
hurt my eyes", gray text on white strains /my/ old eyes because of the
unnecessarily low contrast.

Just use the user agent's text color, because users know best.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
 contrib/css/216light.css | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/css/216light.css b/contrib/css/216light.css
index 741214c..9abdd16 100644
--- a/contrib/css/216light.css
+++ b/contrib/css/216light.css
@@ -4,7 +4,7 @@
  * Suitable for print, and blinding people with brightness.
  * Haphazardly thrown together because bright colors hurt my eyes
  */
-* { font-size: 100%; font-family: monospace; background:#fff; color:#333 }
+* { font-size: 100%; font-family: monospace; background:#fff; }
 pre { white-space: pre-wrap }
 
 /*
-- 
2.25.1

  parent reply	other threads:[~2021-09-01  1:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 16:46 lore.kernel.org upgrade: Sep 1, 2021 Konstantin Ryabitsev
2021-08-30 17:47 ` Rob Herring
2021-08-30 18:04   ` Konstantin Ryabitsev
2021-09-01  1:23 ` Darrick J. Wong [this message]
2021-09-01  9:28   ` Josh Triplett
2021-09-01 13:44   ` Konstantin Ryabitsev
2021-09-01 13:12 ` Sebastian Andrzej Siewior
2021-09-01 13:25   ` Konstantin Ryabitsev
2021-09-15 12:05     ` Sebastian Andrzej Siewior
2021-09-15 12:15       ` Konstantin Ryabitsev
2021-09-15 13:00         ` Sebastian Andrzej Siewior
2021-09-15 13:04           ` Konstantin Ryabitsev
2021-09-02 18:45 ` Guenter Roeck
2021-09-02 18:56   ` Konstantin Ryabitsev
2021-09-02 19:12     ` Guenter Roeck
2021-09-09  9:58 ` David Howells
2021-09-09 12:31   ` Konstantin Ryabitsev
2021-09-09 12:50     ` Steven Rostedt
2021-09-09 13:21     ` Geert Uytterhoeven
2021-09-09 14:33       ` Theodore Ts'o
2021-09-09 14:48         ` Konstantin Ryabitsev
2021-09-09 13:54   ` David Howells
2021-09-09 14:37     ` Konstantin Ryabitsev

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210901012310.GL4159675@sweaglesw.org \
    --to=djwong+korg@djwong.org \
    --cc=djwong@djwong.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@linux.kernel.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.