[wp-meta] [Making WordPress.org] #5690: Very low link contrast in email

Making WordPress.org noreply at wordpress.org
Tue Apr 6 01:32:36 UTC 2021


#5690: Very low link contrast in email
-------------------------------+----------------------
 Reporter:  Otshelnik-Fm       |       Owner:  (none)
     Type:  defect             |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Version Control    |  Resolution:  invalid
 Keywords:  reporter-feedback  |
-------------------------------+----------------------
Changes (by dd32):

 * keywords:   => reporter-feedback
 * resolution:   => invalid
 * status:  new => closed
 * component:  Plugin Directory => Version Control


Comment:

 The styling of the `a` tag here appears to be coming from your mail
 client, not from the default trac/svn html styling.

 Looking at an example message in my inbox, Gmail strips a lot of the
 styles, but I can see the following in the source:

 {{{
 <style>
 #msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px;
 color: #fff; }
 ...
 #msg dl a:link    { color:#fc3; }
 #msg dl a:active  { color:#ff0; }
 #msg dl a:visited { color:#cc6; }
 ...
 </style>
 ...
 <div id="msg">
 <dl class="meta">
 <dt>Revision</dt> <dd><a
 href="http://plugins.trac.wordpress.org/changeset/12345">12345</a></dd>
 }}}

 Note that:
  - The custom link styles aren't being applied in your cae
  - Gmail is stripping both the link colour and the background colour for
 me
  - The class on the `<a>` tag `daria-goto-anchor` is not present in the
 emails WordPress.org sent, and appears to be added by your mail client.

 In the past I've used chrome extensions to alter SVN emails to add colour
 highlighting, you could probably do that here, or to strip the background
 colour out of it instead.

 Since I know we don't have a custom email template in use here (It's just
 the default HTML mode of `svnnotify` - It allows including an external CSS
 file, but I think that's got less compatibility than the existing styles,
 and we can't alter the `<a>` tag directly I don't think), I'm going to
 close this as invalid as it appears to be working as intended, and is more
 likely a client bug, or a bug that should be reported upstream to
 `svnnotify`.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5690#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list