From: Ihor Radchenko <email@example.com>
To: Alexandre Duret-Lutz <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org
Subject: Re: Org 9.5 broke the rendering of my SVG images
Date: Fri, 14 Oct 2022 16:17:28 +0800 [thread overview]
Message-ID: <875ygmzunb.fsf@localhost> (raw)
Alexandre Duret-Lutz <email@example.com> writes:
> In Org 9.5, SVG images started being exported by the HTML exporter as
> <img> rather than <object>.
> The patch causing that was
> with two arguments:
> 1) <object> do not have an alt attribute
> 2) <object> will not render some SVG file correctly if it has no viewBox
> (I'm assuming that the issue shown in that message is a missing viewBox).
> The reason I've noticed this change is that it broke my web pages. On
> my pages, I use SVG to display many automata, and they all share a
> common stylesheet. That stylesheet is not inlined into the SVG, rather,
> it is a separate file included in the SVG files with
> <?xml-stylesheet href="filename.css" type="text/css"?>
> so that the browser only need to download it once.
> Infortunately, <img> does not allow external stylesheets to be
> processed, so my stylesheets are now ignored. Note that one can also
> build SVG images that include other SVG images, or SVG images that have
> animations that start when you hover on some elements. All those
> usages would break with <img>.
> I've seen that very issue was discussed back in 2016
> where Christian Moe pointed out exactly this:
>> (2) You can also do other things with <object> that you cannot with
>> an external stylesheet (linked from the SVG, not the web page).
> So in the interest of allowing users to build documents where SVG
> files are not static, self-contained images, it seems to me that Org
> probably needs some way to specify whether SVG images should be
> exported as <img> or <object> (or maybe even inlined).
This is clearly a regression and should be fixed.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-10-14 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 14:17 Org 9.5 broke the rendering of my SVG images Alexandre Duret-Lutz
2022-10-14 8:17 ` Ihor Radchenko [this message]
2022-10-17 13:32 ` Chris Clark
2022-10-17 13:49 ` Timothy
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).