SVGs from Inkscape do not display correctly in Firefox or EoG
Hi there,
I already asked at my employee company (Red Hat) and Ask Fedora, so far got no useful answers. I even created a bug on Fedora (link later in this message)
I'm a long time Fedora user and occasional Inkscape user. My main use of inkscape is post-processing of SVG files generated by online tools such as google slides. On Fedora 40 and Inkscape 1.3.2 I find that Firefox and Google Chome cannot render SVGs from Inkscape. They display an empty/white page. And Eye of Gnome displays the same files as an empty transparent background.
Issues and workarounds I found on google, such as exporting to SVG 1.1 and configuring preferences related to paths on SVG 1.1 didn't make any difference.
To check that I was not crazy, I created a VM with Inkscape 1.1.1 (from RHEL 9) and files from that, strarting from the same google slide, work well on both the older Firefox in that VM and the newer Firefox on my Fedora machine. It seems to be an issue from Inkscape itself.
It may be someting specific to SVG files creates from Google Slides. Funny thing is that, a few months ago, SVGs from google wouldn't display in web browser, and would work only after cleaning from Inkscape. Now it's the opposite: the files from google do work as-is, but stop working after cleaning from Inkscape.
I opened 2313610 - SVG files from Inkscape don't render in a web browser (nor eog) 4 [1] on Fedora bugs about this issue. It contains two test files, one the export from google slides, other after edits by Inkscape.
On the Fedora forums, someone proposed a proprietary tool, Boxy SVG. It can take the file from google slides and make edits, and the results from it work on both EoG and Firefox. But it lacks many features I'm used to from Inkscape, and I'd prefer staying with open source software. And Boxy fails to display files from Inkscape, displaying an empty write rectangle, just like firefox and chrome do.
So is this a bug or regression with Inkscape itself? Or something specific to Fedora's build? I got the same issues with both the Flatpack and the RPMs from Fedora.
[]s, Fernando Lozano
Links: ------ [1] https://bugzilla.redhat.com/show_bug.cgi?id=2313610
Dear Fernando Lozano,
This issue was reported 4 years ago here: https://gitlab.com/inkscape/inkscape/-/issues/1392
The problem still needs to be fixed in Inkscape, it's creating groups in the clipPath object, which shouldn't be possible.
Please report any issues directly to https://inkscape.org/report/ don't worry about duplicates and thanks for letting us know about this new vector that has the same issue. I think we should raise the priority to high since it's not exactly data loss, but it's close.
For now, remove the clip on the group BEFORE ungrouping. This will fix the issue from google slides.
Best Regards, Martin Owens
On Tue, 2024-09-24 at 16:28 -0300, Fernando Lozano wrote:
Hi there, I already asked at my employee company (Red Hat) and Ask Fedora, so far got no useful answers. I even created a bug on Fedora (link later in this message) I’m a long time Fedora user and occasional Inkscape user. My main use of inkscape is post-processing of SVG files generated by online tools such as google slides. On Fedora 40 and Inkscape 1.3.2 I find that Firefox and Google Chome cannot render SVGs from Inkscape. They display an empty/white page. And Eye of Gnome displays the same files as an empty transparent background. Issues and workarounds I found on google, such as exporting to SVG 1.1 and configuring preferences related to paths on SVG 1.1 didn’t make any difference. To check that I was not crazy, I created a VM with Inkscape 1.1.1 (from RHEL 9) and files from that, strarting from the same google slide, work well on both the older Firefox in that VM and the newer Firefox on my Fedora machine. It seems to be an issue from Inkscape itself. It may be someting specific to SVG files creates from Google Slides. Funny thing is that, a few months ago, SVGs from google wouldn’t display in web browser, and would work only after cleaning from Inkscape. Now it’s the opposite: the files from google do work as-is, but stop working after cleaning from Inkscape. I opened 2313610 – SVG files from Inkscape don't render in a web browser (nor eog) 4 on Fedora bugs about this issue. It contains two test files, one the export from google slides, other after edits by Inkscape. On the Fedora forums, someone proposed a proprietary tool, Boxy SVG. It can take the file from google slides and make edits, and the results from it work on both EoG and Firefox. But it lacks many features I'm used to from Inkscape, and I'd prefer staying with open source software. And Boxy fails to display files from Inkscape, displaying an empty write rectangle, just like firefox and chrome do. So is this a bug or regression with Inkscape itself? Or something specific to Fedora's build? I got the same issues with both the Flatpack and the RPMs from Fedora. []s, Fernando Lozano _______________________________________________ Inkscape Users mailing list -- inkscape-user@lists.inkscape.org To unsubscribe send an email to inkscape-user-leave@lists.inkscape.org
Hi Fernando,
SVGs are text files, you could try narrowing down the problem by comparing their contents manually or using tools like diff.
Also, can you post example files that are as simple and similar as possible that work and don't work so we can have a look at them?
Cheers, Tobias
Am 24.09.24 um 21:28 schrieb Fernando Lozano:
Hi there,
I already asked at my employee company (Red Hat) and Ask Fedora, so far got no useful answers. I even created a bug on Fedora (link later in this message)
I’m a long time Fedora user and occasional Inkscape user. My main use of inkscape is post-processing of SVG files generated by online tools such as google slides. On Fedora 40 and Inkscape 1.3.2 I find that Firefox and Google Chome cannot render SVGs from Inkscape. They display an empty/white page. And Eye of Gnome displays the same files as an empty transparent background.
Issues and workarounds I found on google, such as exporting to SVG 1.1 and configuring preferences related to paths on SVG 1.1 didn’t make any difference.
To check that I was not crazy, I created a VM with Inkscape 1.1.1 (from RHEL 9) and files from that, strarting from the same google slide, work well on both the older Firefox in that VM and the newer Firefox on my Fedora machine. It seems to be an issue from Inkscape itself.
It may be someting specific to SVG files creates from Google Slides. Funny thing is that, a few months ago, SVGs from google wouldn’t display in web browser, and would work only after cleaning from Inkscape. Now it’s the opposite: the files from google do work as-is, but stop working after cleaning from Inkscape.
I opened 2313610 – SVG files from Inkscape don't render in a web browser (nor eog) 4 https://bugzilla.redhat.com/show_bug.cgi?id=2313610 on Fedora bugs about this issue. It contains two test files, one the export from google slides, other after edits by Inkscape.
On the Fedora forums, someone proposed a proprietary tool, Boxy SVG. It can take the file from google slides and make edits, and the results from it work on both EoG and Firefox. But it lacks many features I'm used to from Inkscape, and I'd prefer staying with open source software. And Boxy fails to display files from Inkscape, displaying an empty write rectangle, just like firefox and chrome do.
So is this a bug or regression with Inkscape itself? Or something specific to Fedora's build? I got the same issues with both the Flatpack and the RPMs from Fedora.
[]s, Fernando Lozano
Inkscape Users mailing list -- inkscape-user@lists.inkscape.org To unsubscribe send an email to inkscape-user-leave@lists.inkscape.org
Fernando Lozano said on Tue, 24 Sep 2024 16:28:56 -0300
I opened 2313610 - SVG files from Inkscape don't render in a web browser (nor eog) 4 [1] on Fedora bugs about this issue. It contains two test files, one the export from google slides, other after edits by Inkscape.
For the most part, I've stopped rendering SVG inside browsers, for performance reasons. On anything but the simpler SVGs, the time it takes the browser to go through all the transitions on transitions on transitions takes seriously finite time.
I convert to JPG, or if I need more quality PNG, and show the converted file in the web page.
SteveT
Steve Litt
Hi Steve / all,
On Fri, 27 Sep 2024 18:49:06 -0400 Steve Litt slitt@troubleshooters.com wrote:
Fernando Lozano said on Tue, 24 Sep 2024 16:28:56 -0300
I opened 2313610 - SVG files from Inkscape don't render in a web browser (nor eog) 4 [1] on Fedora bugs about this issue. It contains two test files, one the export from google slides, other after edits by Inkscape.
For the most part, I've stopped rendering SVG inside browsers, for performance reasons. On anything but the simpler SVGs, the time it takes the browser to go through all the transitions on transitions on transitions takes seriously finite time.
I convert to JPG, or if I need more quality PNG, and show the converted file in the web page.
Note that there is also WebP and similar formats, which are smaller than JPEG and PNG, and look better and crispier than JPEG: https://www.shlomifish.org/meta/FAQ/site_loads_quickly.xhtml .
SteveT
Steve Litt
http://444domains.com _______________________________________________ Inkscape Users mailing list -- inkscape-user@lists.inkscape.org To unsubscribe send an email to inkscape-user-leave@lists.inkscape.org
participants (5)
-
Fernando Lozano -
Martin Owens -
Shlomi Fish -
Steve Litt -
Tobias Damisch