Wednesday, September 03, 2008

Telerik Watch Minute: Google Chrome and RadControls

This week we take a quick look at Google's brand new browser, Google Chrome. Actually, it's Google's new beta browser, but I guess at this point Google and beta products go hand-in-hand. In the longest Telerik Watch Minute thus far (about 7 minutes), we look at some of the developer oriented features of Chrome and check out some of the RadControls for ASP.NET AJAX to make sure they still behave as expected. To see what happens, watch the video!

8 comments:

Asit said...

Silverlight doesn't work properly.

Asit said...

Also, few Google Gadgets hang. Particularly the ones that to an Ajax callback.

Todd Anglin said...

@Asit- Correct. I will be addressing this in another video soon. In the mean time, you are correct, Silverlight does not work 100% in the new browser.

Asit said...

Try using this gadget in Chrome:

http://www.google.com/ig/directory?hl=en&url=www.justthinkart.com/googlegadgets/student.xml

It hangs after you click on a thumbnail.

Asit said...

It's very cool browser tho'. And knowing Google, they will do a great job.

Every developer should include it as a "certified browser" for their application.

Anonymous said...

The RadCombobox blows up when I try to select an item and the whole page. It has autopostback enabled.


radC:RadComboBox

ID="loadedaddresses" Width="200px" Visible="false" runat="server" SkinsPath="~/RadControls/ComboBox/Skins"
Height="120px" MaxLength="20" Skin="WindowsOlive" Sort="Ascending" MarkFirstMatch="True" OnSelectedIndexChanged="loadedaddresses_SelectedIndexChanged" AutoPostBack="True" DataTextField="ToAddressString" DataValueField="ToAddressString">

radC:RadComboBox

Todd Anglin said...

@Anon- I haven't been able to "blow-up" the RadCombobox in Chrome yet. I have observed a few wacky behaviors with the MarkFistMatch="True", but it turns out those behaviors exist in Safari, too (guess we need to address that). Our devs are definitely working to identify all issues so that we can provide official support for Chrome before the browser ships.

Anonymous said...

I tracked the combobox problem down to state or the text in the combobox:
int ind = loadedaddresses.FindItemIndexByText(e.Text);

The FindItemIndexByText is returning a -1, whilst on other borwsers it returns the correct index.