I'm sure this questions has been asked many times, but I'm not sure I've seen a definitive answer.
I just finished some testing of our application that uses the UltraWebGrid, 2009 Volume 2 on the IE9 Beta. We use a few infragistics controls and everyhting seems fine so far except for the UltraWebgrid. We have a few pages where data can be edited in the grid and there is some AJAX involved. I all cases the grid seems to freeze after data is entered or edited in one cell. The first edit works fine - including the AJAX functionality. After that, the grid seems to freeze and eventually no data can be entered. There are no javascript errors indicated but it seems like some sort of javascript issue.
I still have a subscription so I could upgrade to the latest realease, but from what I read the controls that are now called the ASP.NET Classic controls are no longer changing. Am I going to be forced to update the application and move to the new version of the grid control? This is going to be quite time consuming but if that's the way it is - so be it.
I'm really just looking for some guidance as to what my options are. It seems that if the UltraWebGrid is not going to be compatible with IE9 then I must do something.
Here is a little more information. The same behavior can be found in IE9 beta when using the Infragistics example application. If you go to theis site:
http://samples.infragistics.com/2009.2/WebFeatureBrowser/
Go into ASP.NET -> WebGrid -> Editing Data -> Client-side Cell Edit
Enter data into a couple cells and hit the Enter key. After entering data in one or two cells the grid is locked and you can no longer edit anything. This is the same behavior we are seeing in our application.
Hello wamanring,
We are considering to include new browser support for the old toolset. It depends on that what resources are needed to support new browsers after they are lunched on the market. Once we make a decision it will be announced on the Infragistics website. Please keep track of updates on Supported Environments page: http://es.infragistics.com/support/supported-environments.aspx#SupportedEnvironments
Best Regards
If I read that page, it seems that the UltraWebGrid will not be updated to work with IE9.
Will it or won't it?
The text in question:
In addition to this support lifecycle for the classic controls, we will not be adding support for new browsers or operating systems for the classic ASP.NET controls after the 2010.1 release. This does not affect the extensive OS and browser testing and support we have for the Aikido controls, so rest assured you will still see our controls work as expected in modern browsers like Internet Explorer, Fire Fox, Chrome and Safari.
That's right. We are having the same problems. We are using version 2009.2 UltraWebGrid and customers are reporting that their sites are not working anymore with IE9. Because of the lack of support for older versions (at Infragistics) we are now in the middle of a storm deciding who should cover the costs of changing the defective controls. From a developers point of view this situation is very frustrated and by my concern I would not use 3th party plugins. I am still hoping for a miracle.
I too am waiting for the miracle but unfortunately Infragistics have seriously let us down here. I think they have underestimated how much of a bad taste this is going to leave.
I cannot fathom why they were unable to get a release out to coincide with the IE9 RC.
Cheers, Rob.
"I think they have underestimated how much of a bad taste this is going to leave."
Couldn't agree more.
I have just spent the past couple of weeks unsuccesfully attempting to migrate an existing application from the UtraWebGrid to the WebDataGrid (among other controls). It has been an extremely unproductive, frustrating, unmitigated disaster. The new controls are buggy (I have outstanding support requests...but no actual helpful support from Infragistics) and severly lacking in features when compared to the older asp.net controls. I can appreciate that the new controls use a different framework and will require changes. But removing functionality is simply not acceptable if you expect your customers to migrate to new controls. How are we supposed to migrate to the new controls when they don't offer the same performance or capabilities of the old controls?
Given the delay in support for ie 9, and Microsoft's announcements of IE 10 today, why would those of us depending on the older more functional controls continue to use Infragistics products? Should we interpret the statement that the Ultrawebgrid will soon be retired as an indication that it won't be updated to support the announced IE 10?
It increasingly sounds like our development team would unfortunately be better served moving to a competitor's product rather than wasting any more time and effort with Infragistics since the new controls don't offer the features we need and the old controls (which do) won't be supported going forward.
There appears to have been a release for ASP.NET 10.1 that was posted on April, 15th.
http://es.infragistics.com/DhtmlPanelFrame.aspx?id=12865#ServiceReleases
Does this update fix the issues with IE9 and the UltraWebGrid?
Communication on this has just been terrible.
The update seems to be doing the trick.
Here's where they posted the "announcement" (if you want to call it that):
http://community.infragistics.com/blogs/taz_abdeali/archive/2011/04/04/ie9-and-firefox-4-support.aspx
Supposedly it works in Firefox 4 as well. Haven't tested that, still doing QA on IE 7/8/9
There is no need for the "on this" qualifier. Communication about EVERYTHING from Infragistics is terrible of late.
I've become convinced that friends don't let friends use Infragistics controls because they are buggy, feature lacking, and pathetically supported.
I really hope so as the number of disgruntled emails I'm getting daily now from my clients is getting embarassing.
Rob.