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).
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)
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.
Thanks all for your responses. Apologies for the delay in my own response.
I sincerely hope that we can get the Webkit issues sorted ASAP. Chrome already has over 1% of the web browser market share, it's advertised on the Google front page and takeup for it is growing substantially. I will need some grid replacement pretty quickly - I assume that I'll hae to get up to speed on the new Aikido framework? Is it much different?
My requirements are modest. I just need to be able to set up the grid and display it programatically, perhaps doing some sorts and responding to basic click events. Reckon it'll be a straightforward drop in replacement?
Of course, we have already started talking inside the development team and I can assure you this will be with higher priority (but still, we will need time before we make an official statement about that).
Just wanted to let you know, that we have a great customer feedback
form, where you can suggest feature request (or even new products or something general, like Google Chrome support along our whole product line)
directly to our Product Management team. The link is here:
scans all feature requests submitted via this form and
chances are that this will be included at one point in subsequent
releases. We take customer feedback very seriously, and from what I am
seeing, most if not all of our TODO list is based on features requested
As far as WebDataGrid goes, sure - I think even now the CTP covers all of your requirement and I am sure much more will ship in our next release in 2008.3 (expected October)