UPDATE: we're using 2009 2 IG package, for example (web.config snippet): Infragistics35.WebUI.UltraWebGrid.v9.2, Version=9.2.20092.2137
We've started testing our application with IE9 (RC). It seems that there's a JavaScript error rising from IG's components:
As you can see, the problem is from the following code:
if (document.implementation && document.implementation.createDocument){ igtbl_XSLTProcessor.prototype.__defineGetter__("output", function _igtbl_XSLTProcOutput() {<snip>
When switching to compatibility view (IE7/8), it works ok.
After debugging a little, it seems like the code "document.implementation.createDocument" (see above) was probably meant to filter out IE and to run on mozilla only. However, in IE9 'createDocument' isn't 'undefined', and the next line of code breaks, as "__defineGetter__" is mozilla-only and isn't supported in IE browsers.
Naturally, I'd hate to tell our customers that our recently released web application breaks on the latest IE browser and that they'll have to use Compatibility View.
Please advise A.S.A.P.
I have the same issues with IE9.
This can be fixed by placing the following meta tag in the <head/>, which tells IE9 to mimic IE8.
<meta http-equiv="X-UA-Compatible" content="IE=8" />
No need to use Compatibility Mode.
I am hoping IG comes out with IE9 compatibility soon. It has been in beta going on ages. It seems odd to wait until go live.
Thanks mate.. Saved us heaps of time...
Hi Rob,
Thanks for your reply.
While placing a meta tag to switch to Compatibility View is a possible workaround (although not always working, at least not in IE8), it is hardly an acceptable solution, as it deprives us developers and customers alike from a good, fast and newer engine to run our web applications, and forces us to sticking with older broken browser engines.
I believe that IG should provide a reasonable solution without having us to upgrade to their latest controls, just because several 'if' code statements break now, and without compromising on older browser engines.
UPDATE: The META tag didn't solve the problem. As in IE8, the browser ignored it and continued to run in IE9 mode.