https://bugs.winehq.org/show_bug.cgi?id=40672
Bug ID: 40672 Summary: wine-gecko cannot do xml + xslt on-the-fly transform and display, ie8 can. Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs@winehq.org Reporter: htl10@users.sourceforge.net Distribution: ---
While switching the Font Validator code from COM interop with IE to managed System.Windows.Forms.WebBrowser ( https://github.com/HinTak/Font-Validator/blob/master/FontVal/ResultsForm.cs ) to better support linux mono, and testing under wine for regressions, I remember having problems with all the various combinations on a clean wineprefix - stock wine (i.e. wine-mono), dotnet2 plain, dotnet2 + ie6, + ie7, + ie8 - except dotnet2 + ie8 .
Later I worked out that dotnet2 + ie7 and dotnet2 + wine-gecko would happily display html, just not do xml + xslt on-the-fly transform, which was how the code was originally written (see the history of the above file), hence I now work around the wine problem and moved on.
Another part of the original FontValidator requires genuine dotnet2 (mixed mode assemblies, does not work under wine-mono), but it would be good for wine-gecko to be able to do xml + xslt displays like ie8 does.
Unfortunately I currently tried to detect wine by looking for WINEPREFIX in the environment (line 123 of https://github.com/HinTak/Font-Validator/blob/master/FontVal/ResultsForm.cs ), but you can probably
The pre- COM->managed binary:
https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Va...
the post- COM->managed binary: https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Va...
To test, just fire it up, go to File->Open XML report-> and just load any local web pages, or xml + xslt combo.
Note the dependence on https://bugs.winehq.org/show_bug.cgi?id=30988 - you need genuine dotnet2 to have any embedded webbrowser capability at all - wine-mono is insufficient. This bug is about wine-gecko vs ie8 on top of dotnet2.
I did the FontVal change around the new year, found work-around and moved on, hence the 1.9.0 tag. It probably affects later versions of wine.