From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: [Worg] Proposing a few CSS changes
Date: Sun, 26 Sep 2021 00:46:06 -0500 [thread overview]
Message-ID: <87sfxropnl.fsf@alphapapa.net> (raw)
In-Reply-To: 87o88gdm82.fsf@gmail.com
Hi Timothy,
Timothy <tecosaur@gmail.com> writes:
>> I find it frustrating when I’ve configured my browser to […]
>
> I think this is the source of our differences of opinion. I personally haven’t
> touched my browser’s default CSS, and am not a fan of the default styling, but
> clearly you have changed your browser’s default CSS to something that you find
> works well.
>
> This leads me to a slightly conflicted position, because I both like the idea
> that if the user has set up their browser to use a font they like, a text size
> they like etc. that sites would respect that. But I also suspect that very few
> people ever do this, and am not that happy about how things look with unmodified
> browser defaults. Here I lean towards trying to ensure the best average
> experience, and unfortunately I think that means overriding the default CSS.
No, I haven't changed my browser's default CSS, only the font settings
in preferences. These are standard features, having been present on
browsers for decades, are easily adjusted by any user, and ideally they
should take into account platform defaults as well. These include both
font family and size.
We should keep in mind that the platforms and systems which view the
site are wide and varied. Some users may have high-DPI monitors in dim
environments, others may have low-DPI monitors in bright environments;
some users may have perfect eyesight, while others may be legally blind.
Some users may use an OS that uses strong hinting (e.g. MS-Windows),
while others may use one that does little-to-none (e.g. MacOS). Because
of those factors, there is no good default for us to use; what looks
good on our systems may look very poor or even unreadable to other
users.
So I think it's very important to respect the user's settings,
especially for long texts and documentation (i.e. not the "home page"
parts of Web sites whose purpose is to present projects as a whole).
next prev parent reply other threads:[~2021-09-26 5:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 2:37 [Worg] Proposing a few CSS changes Adam Porter
2021-09-24 8:00 ` Eric S Fraga
2021-09-25 13:58 ` Bastien
2021-09-26 0:25 ` Adam Porter
2021-09-25 19:51 ` Timothy
2021-09-26 0:37 ` Adam Porter
2021-09-26 3:42 ` Timothy
2021-09-26 5:46 ` Adam Porter [this message]
2021-09-26 8:29 ` Stefan Nobis
2021-09-26 8:56 ` Timothy
2021-09-26 10:40 ` Stefan Nobis
2021-09-27 15:45 ` Eric S Fraga
2021-09-27 18:01 ` Thomas S. Dye
2021-09-26 12:12 ` Max Nikulin
2021-10-02 8:17 ` Timothy
2021-10-02 11:11 ` Adam Porter
2021-10-02 11:29 ` Timothy
2021-10-02 12:07 ` Adam Porter
2021-10-02 12:00 ` Eric S Fraga
2021-10-02 18:24 ` Thomas S. Dye
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfxropnl.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).