When using a fresh wine prefix with the latest Wine Internet Explorer 1.7.28, the application I use that embeds IE can not use the html5 canvas element.
When this happens on Windows, a reason is that Windows is conservative about embedding and sets IE into compatibility mode with older versions (like IE 8 ). This is commonly overriden by forcing Windows to embed the latest version:
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
This is what I did in a test html page, and embedded Wine Internet Explorer still shows a user agent of "MSIE 8.0".
When I run the same html page in stand-alone Wine Internet Explorer, it still claims being "MSIE 8.0".
How can I install a modern Internet Explorer? If — as we know — Microsoft's IE9-12 are not supported, it remains only Wine to give some modern web standards for applications that require a modern version of Internet Explorer.
HTML5 canvas in iexplore
Re: HTML5 canvas in iexplore
Fred2 interesting enough you are not seeing what you think you are seeing.
http://wiki.winehq.org/Gecko Wine internet explorer is nothing more than a very hollow shell around winegecko or on other-words a customised version of Mozilla/firefoxs rendering engine that has been modified to lie that is IE. Of course this is feature short in many ways.
Microsoft's IE9-12 are not just feature short you have to remember there are legal questions if you can legally use newer versions of IE in wine.
http://www.validatethis.co.uk/news/fix- ... d-for-all/
The following is not true.
Its not about forcing Window to embed latest version. Prime objective of that instruction is use chrome frame rendering ahead of the IE own engine even if the IE engine is more upto date. Unfortunate is that chrome frame is end of life so that line is exposing users to security issues.
https://developers.google.com/chrome/chrome-frame/
No modern site should contain chrome=1 in the X-UA-Compatible. IE=edge flag might work or might not on real windows. Now when a stack of users don't work suck it up they were insecure. So how do you work around this from an application point of view today. Ship your own browser if the host is too weak use the shipped one.
https://code.google.com/p/chromiumembedded/ and webkit come to mind.
Fred2 welcome to the nasty reality any application depending on the flag set you just used should raise a red flag as being hazard to operations. Even IE=edge so on XP should only ever return MSIE 8.0 on Windows vista MSIE 9.0.... Say hello to super be inconstancy. MSIE 10 and latter was never back-ported to anything before Windows 7.
Fred2 I would say its time to contact the author of application about poor browser handing if they are using the X-UA-Compatible set the way you gave in your example.
http://wiki.winehq.org/Gecko Wine internet explorer is nothing more than a very hollow shell around winegecko or on other-words a customised version of Mozilla/firefoxs rendering engine that has been modified to lie that is IE. Of course this is feature short in many ways.
Microsoft's IE9-12 are not just feature short you have to remember there are legal questions if you can legally use newer versions of IE in wine.
How often I see people getting this wrong its not funny.<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
http://www.validatethis.co.uk/news/fix- ... d-for-all/
The following is not true.
"This is commonly overriden by forcing Windows to embed the latest version:
Its not about forcing Window to embed latest version. Prime objective of that instruction is use chrome frame rendering ahead of the IE own engine even if the IE engine is more upto date. Unfortunate is that chrome frame is end of life so that line is exposing users to security issues.
https://developers.google.com/chrome/chrome-frame/
No modern site should contain chrome=1 in the X-UA-Compatible. IE=edge flag might work or might not on real windows. Now when a stack of users don't work suck it up they were insecure. So how do you work around this from an application point of view today. Ship your own browser if the host is too weak use the shipped one.
https://code.google.com/p/chromiumembedded/ and webkit come to mind.
Fred2 welcome to the nasty reality any application depending on the flag set you just used should raise a red flag as being hazard to operations. Even IE=edge so on XP should only ever return MSIE 8.0 on Windows vista MSIE 9.0.... Say hello to super be inconstancy. MSIE 10 and latter was never back-ported to anything before Windows 7.
Fred2 I would say its time to contact the author of application about poor browser handing if they are using the X-UA-Compatible set the way you gave in your example.
Re: HTML5 canvas in iexplore
Thank you for the reply!
The `chrome` flag was out of place, and Chrome frame is not installed. The intention was mainly about `edge` (to get latest IE mode, if possible > 8 ). I corrected the doctype to html5, but still canvas is not supported and user agent contains MSIE8.0. The application I use embeds an IE control as provided by the operating system. Users can via extensions display content in this browser window, so I have no further control than tweaking the doctype and meta tags of the displayed website.
I'm totally ok (or even happy) that gecko is used, and I know it leaks through some fancy CSS3 features that IE8 does not have. But since I cannot (and probably won't soon be able to) install a more modern version of original MSIE, I was hoping gecko has nevertheless similar features as in Firefox. Should winegecko theoretically have html5 canvas, or does the hollow shell hide or not yet implement certain features?
The `chrome` flag was out of place, and Chrome frame is not installed. The intention was mainly about `edge` (to get latest IE mode, if possible > 8 ). I corrected the doctype to html5, but still canvas is not supported and user agent contains MSIE8.0. The application I use embeds an IE control as provided by the operating system. Users can via extensions display content in this browser window, so I have no further control than tweaking the doctype and meta tags of the displayed website.
I'm totally ok (or even happy) that gecko is used, and I know it leaks through some fancy CSS3 features that IE8 does not have. But since I cannot (and probably won't soon be able to) install a more modern version of original MSIE, I was hoping gecko has nevertheless similar features as in Firefox. Should winegecko theoretically have html5 canvas, or does the hollow shell hide or not yet implement certain features?
Re: HTML5 canvas in iexplore
http://wiki.winehq.org/BuildingWineGecko
Fred2 wine gecko is a sub project in it own right.
Remember over 20 percent of the Windows userbase is still XP. So you are going to be in hell with upset users.
Fred2 it is worth opening up a bug report and linking applications in the appdb that need it.
Fred2 wine developers really like having the application that is causing issues so they can test. You can fairly much winegecko is always going to be short of browser features as they are implemented on reported need. winegecko is not trying to be a universal browser.
Basically running program in wine using IE interfaces is going to cause you on going misery.
Fred2 wine gecko is a sub project in it own right.
The holllow shell in wine does not implement much at all. Winegecko and items like html5 canvas and the useragent returned is decided by Winegecko.Should winegecko theoretically have html5 canvas, or does the hollow shell hide or not yet implement certain features?
It would require changing winegecko to change version of Internet explorer returned. Wine gecko behaves at this stage like XP does so the highest version it should return is MSIE8.0 even if it gets a "IE=edge" instruction. That is the big problem. It needs updates and the "IE=edge" result has be Windows version dependant.user agent contains MSIE8.0
Remember over 20 percent of the Windows userbase is still XP. So you are going to be in hell with upset users.
Fred2 it is worth opening up a bug report and linking applications in the appdb that need it.
Fred2 wine developers really like having the application that is causing issues so they can test. You can fairly much winegecko is always going to be short of browser features as they are implemented on reported need. winegecko is not trying to be a universal browser.
Basically running program in wine using IE interfaces is going to cause you on going misery.
