I've got a problem. One of the datagrids a website which I am developing, doesn't show any rows >ever< when viewed under the new Google Chrome browser that was released earlier today.
Has anyone else noticed any inconsistences with the Infragistics controls and Google Chrome?
I've published two screenshots on my review of Google Chrome here: http://blog.evolvedsoftwarestudios.com/2008/09/02/web-browser-wars-room-for-one-more-google-launch-google-chrome/ (scroll right down to the last two images in the article).
Hello,
I have just gone through your blog post - great content there. I also was probably one of the first to download and try Google Chrome and I am really impressed by the speed and simplicity of the browser, plus several great ideas they have to save space (pressing Ctrl +K for search goes back to address bar with ? prefix - clever stuff).
Google Chrome's engine is based on WebKit - this is the open source engine that powers the Safari browser. So while we of course cannot make any official statements for Chrome at this very moment, you will typically expect the controls we ship that work on Safari to generally work in Chrome. UltraWebGrid has parts of it that are not working on Safari yet, hence the problem you experience.
Needless to say, Safari and Google Chrome support will be moving up the priority list and we will do our best to be better in this area. In fact, almost 100% of the stuff we will be going to ship soon already works fine in both Chrome and Safari - you can test this with the CTP versions of WebDataTree and WebDataGrid and our brand new Drag & Drop framework here (a lot of this stuff and much more will ship in the next releases we have)
https://es.infragistics.com/samples/aspnet/drag-drop-framework/overview
So basically - yes, we are watching Chrome (and WebKit / Safari in general) closely and will be doing our best to support that, the way we support FireFox/Mozilla and IE.
The Aikido grid (WebDataGrid) will not be backwards compatible with UltraWebGrid, but this is not necessarily a bad thing. It's a brand new grid product, built from scratch, that will employ the latest technologies and what we have learned from the past. It is built with performance and extensibility into account.
Needless to say, this does not mean that we will be actively developing UltraWebGrid as well - it is just that I cannot currently commit to a timeframe for official full Chrome support, but I do assure you that we are looking at that seriously and this will be moving up the priority list soon.
I think we're out of luck re: Chrome and the UltraWebGrid. It never seems to be on the Infragisitcs urgent radar and their response is re-code to use the newer AJAX grid.
Rob.
Hello Support Team, We're currently using Infragistics 2010 Vol 2 and as our application has already implemented the UltraWebGrid when working with version 2008. We've noticed that the UltraWebGrid is not working with the Safari and also Google Chrome browsers even with the current version. Is there any way to get this working with Google Chrome and Safari?RegardsShahin
I am currently using 10.2, and the older grid only supports IE and Firefox. I have started moving to the newer grids, and honestly find them a lot more intuitive. Personally the new grids do everything that I need, which is edit in the grid, sorting, filtering, paging, custom appearance, etc. Obviously your situation might not allow you to move to the new grids, but if it does I found that it was pretty easy to do.
Is there any updated information on getting the UltraWebGrid to be compatible with Chrome? We're looking at the 2010 releases now, I'm wondering if this fix has been implemented yet?
I agree with this sentiment. Sure, you'd love us all to shift to the new controls but the time to do this is not always a luxury one has in real life.
I'm also a pessimist when it comes to switching to new controls. I have a sneaky feeling that some neat feature I use in UltrawebGrid won't have made it to the new grid yet... Is there a property/method comparision between the two grids?
So I'd like to see the legacy controls supporting Google Chrome.
That said, one of the big advantages of Chrome is the speed of JavaScript and if IE9 lives up to it's promises, Chrome will be given a run for it's money in this area.
Cheers, Rob.