Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
515
IE9 and Infragistics ASP.NET 2009.2 __defineGetter__
posted

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.

 

Parents Reply
  • 515
    posted in reply to Rob Hudson

    Hi Rob,

    No disrespect, but you're welcome to read about sbeelers attempts to migrate to WebDataGrid in Taz's post (comment from 04-12-2011).

    I think that your opinion ("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?") is problematic and can be referred back at you: You're using WebDataGrid now, but what happens if IG decides to "retire" it in the future in favor of a newer grid, and a new IE comes out and everything breaks? Are you going to invest precious time and money to upgrade to a newer grid? This might be easy if you simply display a bunch of data, but the grids have other complex functionalities which, if used, easily break. More likely you'll attempt to use a compatibility mode to get over these issues.

    I guess that if IG decided to "retire" their grid, they'll probably retire more controls from previous infrastructures. I'm unfamiliar with IG's new controls, but since MS is going to "retire" their client libraries in favor of jQuery, it's possible that in the future we will see another "retirement" of controls from IG. What then?

    Finally, although I'm happy that IG decided to provide a service release handling this issues, my attempts so far (several hours of work....) fail to witness any changes over here and the problems still occur (I posted about this in Taz's post and also emailed him a tester to reproduce these issues).

     

Children