all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 27086@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#27086: perhaps always use a white background when viewing transparent PNGs etc.
Date: Sun, 29 Sep 2019 18:00:43 +0200	[thread overview]
Message-ID: <87sgofdrdg.fsf@gnus.org> (raw)
In-Reply-To: <87zhinglrf.5.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Sun, 29 Sep 2019 23:33:40 +0800")

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> LI> Then there's nothing we can do here -- the PNG itself is badly made
> LI> (instead of using alpha channels it's just marking pixels as either
> LI> fully transparent or fully opaque).
>
> Well looks great in Firefox.
> Firefox always does the right thing.

Sounds like Firefox defaults to white backgrounds on these images, but
if the PNG had been constructed the other way (towards black), then that
would have looked equally bad.

So it doesn't seem like there's anything we can do here.

Did you forward the original PNG file to the bug tracker?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-09-29 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 13:37 bug#27086: perhaps always use a white background when viewing transparent PNGs etc 積丹尼 Dan Jacobson
2017-06-03  3:25 ` npostavs
2017-06-06 19:40 ` 積丹尼 Dan Jacobson
2019-09-29  2:27 ` Stefan Kangas
2019-09-29  4:23 ` 積丹尼 Dan Jacobson
2019-09-29  4:29   ` Stefan Kangas
2019-09-29  4:59 ` 積丹尼 Dan Jacobson
2019-09-29 10:27   ` Lars Ingebrigtsen
2019-09-29 15:33 ` 積丹尼 Dan Jacobson
2019-09-29 16:00   ` Lars Ingebrigtsen [this message]
2019-09-29 16:08 ` 積丹尼 Dan Jacobson
2019-09-29 16:11   ` Lars Ingebrigtsen

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

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

  git send-email \
    --in-reply-to=87sgofdrdg.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=27086@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=npostavs@users.sourceforge.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.