unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: rcopley@gmail.com, johnw@gnu.org, tom@tromey.com, emacs-devel@gnu.org
Subject: Re: CSS contrast (#30295) (was Re: Heads-up: Emacs 26.1 RC1)
Date: Wed, 21 Mar 2018 09:54:49 +0200	[thread overview]
Message-ID: <834ll9lv7a.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8U4r5fhRRi=4O2RDAJSuFNzgRzgp0my+zi9PLvpobPOXA@mail.gmail.com> (message from Yuri Khan on Wed, 21 Mar 2018 12:52:15 +0700)

> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Wed, 21 Mar 2018 12:52:15 +0700
> Cc: Eli Zaretskii <eliz@gnu.org>, John Wiegley <johnw@gnu.org>,
> 	Tom Tromey <tom@tromey.com>, Emacs Development <emacs-devel@gnu.org>
> 
> Why not use the WCAG contrast ratio formula?
> 
> https://www.w3.org/TR/WCAG20/#visual-audio-contrast
> 
> (Except that, if implemented literally, it will probably not fit the
> trivial change threshold.)

I have nothing against implementing the WCAG contrast criterion, but
that would certainly need to be done on master, not on the release
branch.  This discussion was about what to do for Emacs 26.1.



  reply	other threads:[~2018-03-21  7:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 19:02 CSS contrast (#30295) (was Re: Heads-up: Emacs 26.1 RC1) Richard Copley
2018-03-20 19:17 ` Eli Zaretskii
2018-03-20 19:56   ` Richard Copley
2018-03-21  5:52     ` Yuri Khan
2018-03-21  7:54       ` Eli Zaretskii [this message]
2018-03-21  7:38     ` Eli Zaretskii
2018-03-21  9:59       ` Richard Copley
2018-03-21 11:34         ` Richard Copley
2018-03-21 12:47           ` Eli Zaretskii
2018-03-21 13:22             ` Richard Copley
2018-03-21 13:32               ` Eli Zaretskii
2018-03-21 14:24                 ` Richard Copley
2018-03-21 15:36                   ` Eli Zaretskii
2018-03-21 19:03                     ` Richard Copley
2018-03-21 12:40         ` 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=834ll9lv7a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=rcopley@gmail.com \
    --cc=tom@tromey.com \
    --cc=yuri.v.khan@gmail.com \
    /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).