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.
Hi all,
Are there anyone who be able to run UltraWebGrid in IE8/IE7 compatibility mode, in IE9 browser?
We are using older version (2007.1) and trying to find a way other than upgrading to the latest version.
We tried to add compability meta tag to several places:
<meta http-equiv="X-UA-Compatible" content="IE=8" />
1- web page's html>head> meta tag is not working.
2- http header to IIS is not working.
3- custom http header to web.config file is not working.
Thanks,
Fatih
ewolfman reported above that the meta tag has to be the first tag in the <head> section, and that if it is placed elsewhere, it may not work.
Also, as a fellow user (not an Infragistics employee), I really recommend upgrading. The WebDataGrid is lightyears ahead of the UltraWebGrid, and the CDN is also very nice.
2007.1 was terrific, but it's for an older generation of browsers, and you're going to have issues as browsers evolve. What happens when you want to use a control from any vendor built for the next generation, and you have all of your pages stuck in IE8 compatibility mode?