unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 51556@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>,
	kevin.legouguec@gmail.com
Subject: bug#51556: 29.0.50; Poor contrast of Customize SVG icons with dark backgrounds
Date: Tue, 2 Nov 2021 20:19:52 +0000	[thread overview]
Message-ID: <YYGdaJLM+u5s0HCf@idiocy.org> (raw)
In-Reply-To: <18066bc0-86a6-5901-9a53-e2c6ea13fbc8@gmail.com>

On Tue, Nov 02, 2021 at 11:43:58AM -0700, Jim Porter wrote:
> 
> 1) Single-color SVGs
> 
> Some SVGs are just a single-color shape, like the Customize arrows. There's
> no *particular* color that's right for these, aside from "what looks good".
> In some ways, these SVGs are like an ordinary textual glyph, except that
> we've defined our own fancy shape to use. In this case, I think it makes
> sense to be able to specify what color to use for the SVG independently of
> the shape so that themes can adjust it as-needed.
> 
> This case is the one initially described in this bug.

This is the case we looked at when we originally replaced the
customize widgets with SVGs. At the time we very intentionally removed
the colour and size information from the SVG files (checkbox.svg, etc)
so that they would match the colours and font size of the surrounding
text.

I guess, unfortunately, these arrows were missed.

-- 
Alan Third





  parent reply	other threads:[~2021-11-02 20:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 17:56 bug#51556: 29.0.50; Poor contrast of Customize SVG icons with dark backgrounds Kévin Le Gouguec
2021-11-01 19:14 ` Eli Zaretskii
2021-11-01 20:10   ` Kévin Le Gouguec
2021-11-02 12:40     ` Eli Zaretskii
2021-11-01 20:49   ` Jim Porter
2021-11-02 12:49     ` Eli Zaretskii
2021-11-02 14:41       ` Stefan Kangas
2021-11-02 14:59         ` Eli Zaretskii
2021-11-02 15:17           ` Stefan Kangas
2021-11-02 15:26             ` Stefan Kangas
2021-11-02 16:38               ` Eli Zaretskii
2021-11-02 16:43                 ` Lars Ingebrigtsen
2021-11-02 17:01                 ` Stefan Kangas
2021-11-02 17:13                   ` Eli Zaretskii
2021-11-02 17:44                     ` Stefan Kangas
2021-11-02 18:01                       ` Eli Zaretskii
2021-11-02 18:43                         ` Stefan Kangas
2021-11-02 18:53                           ` Eli Zaretskii
2021-11-02 19:26                             ` Stefan Kangas
2021-11-02 18:43                         ` Jim Porter
2021-11-02 18:58                           ` Stefan Kangas
2021-11-02 19:15                             ` Eli Zaretskii
2021-11-02 19:44                               ` Stefan Kangas
2021-11-02 20:19                           ` Alan Third [this message]
2021-11-02 22:56                             ` Kévin Le Gouguec
2021-11-04  8:11                             ` Eli Zaretskii

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=YYGdaJLM+u5s0HCf@idiocy.org \
    --to=alan@idiocy.org \
    --cc=51556@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=kevin.legouguec@gmail.com \
    --cc=stefan@marxist.se \
    /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.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).