From: Eli Zaretskii <eliz@gnu.org>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: luangruo@yahoo.com, 54246@debbugs.gnu.org
Subject: bug#54246: 29.0.50; EWW not showing images in some websites
Date: Sat, 05 Mar 2022 09:30:30 +0200 [thread overview]
Message-ID: <83mti4hn55.fsf@gnu.org> (raw)
In-Reply-To: <CAB6f121uy8qv7uGahUzu2XdTVSNDZA3LE=2GijODRXjmi-Xbjw@mail.gmail.com> (message from Payas Relekar on Sat, 5 Mar 2022 12:42:18 +0530)
[Please, no private email. Please use Reply All to reply.]
> From: Payas Relekar <relekarpayas@gmail.com>
> Date: Sat, 5 Mar 2022 12:42:18 +0530
>
> I will be able test with imagemagick once I get to my computer, but if the recommended default is to not do
> so, isn't this a regression? A format once supported by defaults is no longer supported by new defaults, it
> means the replacement wasn't fully ready.
We want to move from ImageMagick because it has stability and
security issues. ImageMagick build is still supported, though.
Emacs 29 also support externally converted images; see
image-use-external-converter and image-converter.el.
We could also support building with libwebp and dav1d; patches
welcome.
next prev parent reply other threads:[~2022-03-05 7:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 16:26 bug#54246: 29.0.50; EWW not showing images in some websites payas
2022-03-04 18:47 ` bug#54246: Payas Relekar
2022-03-05 0:42 ` bug#54246: 29.0.50; EWW not showing images in some websites Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 3:21 ` Payas Relekar
2022-03-05 3:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 6:48 ` Eli Zaretskii
[not found] ` <CAB6f121uy8qv7uGahUzu2XdTVSNDZA3LE=2GijODRXjmi-Xbjw@mail.gmail.com>
2022-03-05 7:30 ` Eli Zaretskii [this message]
2022-03-05 17:57 ` payas
2022-03-05 19:17 ` Lars Ingebrigtsen
2022-03-05 21:23 ` payas
2022-03-05 21:29 ` Lars Ingebrigtsen
2022-03-06 16:42 ` Lars Ingebrigtsen
2022-03-07 9:39 ` payas
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=83mti4hn55.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54246@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=relekarpayas@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).