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?
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).
I understand where you are coming from. I really do. I have almost finished migrating all my grids from UltraWebGrid to WebDataGrid (while maintaining complex functionality), and it's been a horrendous pain in the butt. Still have pages in compatibility mode, and still dealing with isolated migration issues. But having spent months going through this process on a very data-intensive website, I can tell you that it was worth it.
Technology moves forward. I have a choice. I can embrace it, or I can moan about how my classic ASP tools are no longer supported, and the custom ActiveX controls I once built for my websites are now blocked by all browsers. I can moan about how my efforts to do all my processing server-side are outdated because it was once a standard security practice to disable javascript in the client. And where is Infragistics support for clients without javascript anyway? Or, I can embrace change, and I can dive head-first into the shiny new world of XHTML, jQuery, AJAX, and HTML5.
You are right. It is a risk. And it's a lot of work. With no guarantees.Chances are pretty good that 5 years from now, even these new technologies will be outdated. I will be transitioning from these technologies into something entirely new, for the 3D holographic web. And my WebDataGrids will have to be converted to InfraWebDataCubes.
It is time to retire UltraWebGrid in favor of WebDataGrid. The architecture behind WebDataGrid is an evolutionary leap, and it doesn't make sense to maintain two grids in perpetuity. Just as I support Microsoft in moving to jQuery for client development. Just as I support New York City in closing its horse stables feed stores in favor of mechanics and gas stations. It's completely OK for Infragistics to decide not to update UltraWebGrid for IE10. I don't expect my utility company to provide DC power for my old Eddison light bulbs.It's sad that UltraWebGrid's day has gone. If we expected technology to stay still so that we could continue using the same tools in perpetuity, we would still be running Windows 95, programming in ASP, and having this discussion via TELNET on the Infragistics BBS.It's sad that my first programs (which were stored on cassette tape, and you could actually listen to them loading) can't even be loaded onto a modern machine much less executed... but it's the nature of progress. We can either embrace change, or be passed by those who do.
I don't expect IG to stand behind UltraWebGrid forever. Naturally we're all going forward with time and technology. However, I do expect that they provide better response time to IE9 and the problems arising from it in their products. The fact that IG continued to sell UltraWebGrid in their packages all this time, when IE9 Platform Preview 1 was out over a year ago, and that they lacked the response time to provide a suitable Service Release in time - that is what I consider the problem. The fact that they released a Service Release which is supposed to address these problems, shows that they acknowledge that a problem does exist with their products. Unfortunately, this Service Release seems to lack the required support and solutions.
I assume that if you have issues with IE9 on your own products, Rob, you'll do your best efforts to solve them for your customers too.
Finally, their lack of transparency in publishing their plans and handling of the situation is also disturbing. I expect a representative to blog or post at least once a week about the situation of things, rather then the current silence.
Hi Fatih,
I suggest that you either open the Developer Tools where it is written in the top area in what browser mode you are in, or download the Platform Preview from MS where it is written in the bottom status bar. Unfortunately MS doesn't seem to allow downloading the IE9 preview anymore, so I can only hope that Platform Preview 10 isn't too buggy.
If the browser mode is IE8, then you have used the META tag correctly. If not, I suggest that you View Source and see where the META tag was rendered. I had a situation where my code behind added HTML tags before the compatibility meta tag and that's why it wasn't working. IE also warns of a misused meta compatibility tag in the Script window (read this blog post).
Thanks for your suggestions.
I implemented your suggestions to my simple test project, but nothing has changed.
Changing grid cell or sorting a column is problematic and not working after a few attempts for an even simple grid.
Is there any way to look at attached simple project and tell me if you could run it on IE9 or not..
(It requires 2007.1, if you have, i will be much appreciated)
Thanks again,
Fatih.