From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ynyaaa@gmail.com, 47040@debbugs.gnu.org
Subject: bug#47040: 27.1; PNG binary transparency is ignored
Date: Wed, 10 Mar 2021 17:14:09 +0200 [thread overview]
Message-ID: <83tupjniri.fsf@gnu.org> (raw)
In-Reply-To: <87czw7jbgq.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 10 Mar 2021 16:05:25 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 10 Mar 2021 16:05:25 +0100
> Cc: 47040@debbugs.gnu.org
>
> > Red pixels in the both images have 0 for alpha value, so they should be
> > transparent and invisible, but transparent1.png is displayed as a red
> > square with a green frame in a emacs buffer.
> >
> > transparent2.png is displayed as a white square with a green frame as
> > expected.
> >
> > When they are displayed in a chrome browser, inner squares of the both
> > images are displayed as transparent.
>
> I'm unable to reproduce this in Emacs 27.1 in Debian/bullseye, so this
> may be a Windows-specific problem. It may also be fixed in Emacs 28,
> since the transparency code has gotten a lot of work. Would it be
> possible for you to check in Emacs 28 whether this problem is still
> present there?
>
> If not, can somebody else with Windows and Emacs 28 check whether the
> problem is still present?
The problem is still present when using the default libpng, but not if
I use the w32 native image API.
next prev parent reply other threads:[~2021-03-10 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 10:45 bug#47040: 27.1; PNG binary transparency is ignored ynyaaa
2021-03-10 15:05 ` Lars Ingebrigtsen
2021-03-10 15:14 ` Eli Zaretskii [this message]
2021-03-10 22:14 ` Alan Third
2021-03-11 16:53 ` Lars Ingebrigtsen
2021-10-31 14:49 ` Stefan Kangas
2022-06-20 9:46 ` 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=83tupjniri.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47040@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=ynyaaa@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 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.