From: Eric Wong <e@80x24.org>
To: Mateusz Loskot <mateusz@loskot.net>
Cc: meta@public-inbox.org
Subject: Re: Default theme
Date: Fri, 22 Feb 2019 08:50:14 +0000 [thread overview]
Message-ID: <20190222085014.mwvkf2mwrb6yeyrh@dcvr> (raw)
In-Reply-To: <CABUeae_raBW1wpjt8BTB=kp7ecbvBR7WFzPD6jshkABJ=NG7qA@mail.gmail.com>
Mateusz Loskot <mateusz@loskot.net> wrote:
> Hi,
>
> I've noticed the theme has changed, from light to dark,
> while browsing public-inbox.org archives.
There was no theme before, just browser defaults. I mainly use
w3m with a dark terminal, so it was always dark to me.
> Is that permanent change?
I don't know, yet. I've considered making it random, but that's
probably too disruptive and confusing.
I wouldn't say public-inbox.org itself is permanent, though,
either :>
> Is there any way to switch back to light theme as default?
>
> I mean, other than the colors customization via CSS.
"prefers-color-scheme" media queries may be used to set
to respect user preferences in future browsers.
The way I see it is: whatever color scheme I choose will make
some people unhappy. That's why I make sure it's customizable
via user CSS and the CSS class names remain stable.
Note: public-inbox installations do not have a default color
scheme right now. So it's up to the admin to configure it.
next prev parent reply other threads:[~2019-02-22 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 13:36 Default theme Mateusz Loskot
2019-02-22 8:50 ` Eric Wong [this message]
2019-02-22 20:39 ` Dmitry Alexandrov
2019-02-23 2:47 ` Eric Wong
2019-02-23 10:56 ` [PATCH 0/2] ensure user CSS always overrides BOFH CSS Eric Wong
2019-02-23 10:56 ` [PATCH 1/2] usercontent.pm: set "!important" to override BOFH prefs Eric Wong
2019-02-23 10:56 ` [PATCH 2/2] www: prevent '!important' in BOFH-specified CSS Eric Wong
2019-02-23 19:55 ` Default theme Mateusz Loskot
2019-02-22 20:53 ` Mateusz Loskot
2019-02-23 1:19 ` Dmitry Alexandrov
2019-02-23 2:50 ` Eric Wong
2019-02-23 10:49 ` Eric Wong
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=20190222085014.mwvkf2mwrb6yeyrh@dcvr \
--to=e@80x24.org \
--cc=mateusz@loskot.net \
--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).