91 pre msi breaks Chrome SVG render

[Michael Williamson]

I thought I'd give Inkscape 0.91 pre a try yesterday. I downloaded the Windows MSI and installed it. I discovered afterwards that Chrome no longer natively rendered SVG. Any attempt to load and SVG file, either in an image tag or the file itself would cause Chrome to download the file instead of rendering it. I tested this in multiple versions of chrome and found consistent behavior (see below for a list of versions). I also tested this in Firefox, Firefox Developer Edition and Internet Explorer 11 which did not show this behavior. The problem was isolated to Chrome.

I uninstalled Inkscape 0.91 pre and Chrome was restored to properly rendering SVG.

I installed Inkscape 0.91 pre (inkscape-0.91pre2-x64.r13532.20140826)

I am running on Windows 7 Enterprise 64-bit.

I develop for the Chrome Platform, so it is a critical part of my workflow and I'm very familiar with its internals and mechanics. I also have the following versions of Chrome installed:

1) Chrome (currently 39.0.2171.71)
2) Chrome Dev (portable, currently 41.0.2236.0)
3) Chrome Beta (portable, currently 40.0.2214.10)
4) Chrome Stable (portable, currently 39.0.2171.71)
5) Chrome Canary (currently 41.0.2239.0 canary (64-bit))
6) Chromium (currently 41.0.2240.0)

[Shlomi Fish (shlomif-gmail)]

Everything works fine on my Windows 7 x86-64 VM. After I installed and started Inkscape, then Google Chrome displays the SVGs here and here fine - http://svg-wow.org/camera/camera.xhtml ; https://developer.mozilla.org/en-US/demos/detail/svg-clock . I'm not saying the problem does not exist, but I don't see it.

[su_v (suv-lp)]

> I installed Inkscape 0.91 pre (inkscape-0.91pre2-x64.r13532.20140826)

JFYI - this is not the latest (aka current) pre-release build of Inkscape 0.91 (for Windows and other platforms). Please check the Inkscape download page (updated yesterday) for links to the newly uploaded packages:
- Pre-Release Versions (0.91 Pre3):
  http://inkscape.org/en/download/

[Michael Williamson (michael-williamson-r)]

I will install the latest version and test again.

For reference, this video shows the bug in action:
http://youtu.be/FZTXWIOfhnk

[Michael Williamson (michael-williamson-r)]

JFYI, this page is out of date: https://inkscape.org/en/download/windows/

[su_v (suv-lp)]

On 2014-12-05 19:30 (+0100), Michael Williamson wrote:
> JFYI, this page is out of date:
> https://inkscape.org/en/download/windows/

Not outdated per se - packages of the "Development version" (i.e. based on current trunk) listed there are not the same as pre-release packages (based on tarballs created from a tagged revision in the stable release branch). The platform-specific download pages might lack the section about recent pre-release builds (for 0.91) which is only on the main download page. OTOH the pre-release packages are only temporarily available and will be obsolete once 0.91 is released.

[Michael Williamson (michael-williamson-r)]

I've tested with the latest version with the same results.

[su_v (suv-lp)]

On 2014-12-05 19:43 (+0100), Michael Williamson wrote:
> I've tested with the latest version with the same results.

Would you mind sharing which 0.91pre3 package did you download and install? 32bit or 64bit, exe or msi or 7z?

[su_v (suv-lp)]

@theAdib - any chance you could comment on this issue?

[Michael Williamson (michael-williamson-r)]

inkscape-0.91pre3-x64.msi

[Roul P. (perhelion1)]

I can reproduce it also with 0.48 see duplcate bug case bug 1402309

[trlkly (trlkly)]

I don't see a mention of the actual problem in this bug, so I'll describe it.

 A registry setting is changed up on installation of Inkscape 0.48+. That setting is HKEY_CLASSES_ROOT\.svg\Content Type. It is set to "application/svg", when the official MIME-type for SVG is "image/svg+xml." (This option is set correctly by default before installation of Inkscape.)

Firefox appears to ignore the MIME-type in the registry, but Chrome and Internet Explorer do not.

The problem is in the installer, as it does not happen if you use the .7z releases. If I had to guess, it happens when Inkscape sets itself up as the default handler for SVG files, which would be the only time this part of the registry would be touched.

[theAdib (theadib)]

ok, I saw the video. I will investigate. Adib.

[theAdib (theadib)]

seems all .exe type installer are not affected . So this is a problem of the upcomming 0.91 and their .msi installer.

I have uploaded a corrected packaged version 2 of the msi installer for the pre3 relelease:
- inkscape-0.91pre3-x64-2.msi
- inkscape-0.91pre3-2.msi
pls see here: https://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/

could you please test and report if that solves your problem?

regards, Adib.

[Roul P. (perhelion1)]

I've tested the packed, it's working now for me. Thanks you and an happy new year!

[Michael Williamson (michael-williamson-r)]

Just got done testing with inkscape-0.91pre3-x64-2.msi and was delighted to see this fixed.

[su_v (suv-lp)]

On 2015-01-06 18:58 (+0100), theAdib wrote:
> ** Changed in: inkscape
> Status: Triaged => Fix Committed

There are no related commits to be found in inkscape trunk <lp:inkscape> and in the release branch for 0.91 <lp:inkscape/0.91.x> - did you forget to push?

[theAdib (theadib)]

commited to trunk as bzr#13846. "fix for #1399720, win32 msi packaging... "
need probably release maintainer for commiting to inkscape/0.91 .? Who will take this over?

Adib.

[ScislaC (scislac)]

Backported in 0.91.x r13698