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://ko.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.
Hi Taz,
Thanks for responding and giving your insights into the development process. There are a couple of issues that this brings up however:
1. Are the Aikido controls a direct drop-in replacement to the exiting Web Grid controls? The issue is that the Web Grid doesn't work >almost at all< on Chrome (and I assume by implication they are bugged on Safari too). Unfortunately this makes them completely useless for almost all non-intranet web applications as an ever increasing quantity of users migrate to Chrome. What is the relationship between "Aikido" and the current ASP.NET Web controls?
2. Am I right that the next release will not explicitally support Google Chrome but there are plans to thoroughly test on Safari?
I've had to drop Infragistics for the current project I'm working on as the lack of Chrome support is a deal breaker. This is dissapointing since the rest of the Infragistics framework appears to be ok.
Thanks,
Mike
I've answered part of my own question on 1. Aikido Framework. It's the new technology framework from Infragistics. Ok, I got that.
Regarding Aikido's support of Google Chrome and Safari, I can only urge you to make sure that Google Chrome is well tested and supported as many of our customers are starting to adopt it.
Taz-
You mentioned that the WebGrid is coming out with 2008.3 (in Nov). So when is the new UltraWebGrid coming out ... sure aikido is new, shiny, and functional - but it sure gives the community a lot of work to convert projects, etc.
Thanks
Chad
What version of Infragistic UltraWebGrid is supported on Safari 3.0? I see multiple issues when using 2008 V2.
gotoroi,
As listed on the Supported Environments page of our website, WebGrid is currently not supported with Safari.
I recommend using WebDataGrid instead (released in 2008 Volume 3), since our ASP.NET AJAX controls are supported with Safari.
gotoroi-
Vince fails to point out the LIMITED capabilities of the WebDataGrid - which very VERY inferior to the original. I have been told by Taz that the WebGrid will be expanded to include Safari and additional browsers. Or maybe the WebDataGrid will be expanded to include additional functionality (my guess is this is more likely).