You’ve no doubt downloaded or at least heard of Google Chrome already. If you haven’t click here to download it and click here to view Google’s creative comic about the browser. I recommend reading the comic as its very informative and will get you up to speed on why Google’s browser will make every web developer rethink their apps.

But the purpose of this post is to just get some screenshots out there of Google Chrome in action with Sharepoint. I can’t really find that much information currently on browsing Sharepoint sites in Google Chrome, so hopefully some of you will post your thoughts/information on this below.

Let’s also keep in mind that this is obviously a beta, albeit pretty stable, release of a brand-new web browser. There will be new internal builds everyday, so anything in this article could be dated within 30 minutes. With that said, let’s look at how Chrome renders Sharepoint.

Figure 1 – Chrome’s omnibox will attempt to grab related results across the web and locally based on what you type. My testing site is pretty basic, so it didn’t return much.

Figure 2 – As you can see I’m prompted with a login box similar to what is seen when browsing Sharepoint with Firefox.

Figure 3 – A basic Sharepoint site with no customizations. There are some display flaws here, but I will say this. It displays the page much quicker than even IE7, and generally looks better than what I’m used to seeing in Firefox. Firefox still hasn’t been able to display aspx pages (not that it inherently should) nicely. There will need to be a lot more testing of Chrome to see if its better overall, but this is a nice start for a pilot public release.

Figure 4 – A basic MySite page. There a couple more noticeable flaws here, but still I’m optimistic.

The real test will be if Chrome can navigate through the myriad of Microsoft aspx sites as Firefox renders it unusable in most cases. But even the IE8 beta breaks Microsoft sites, live Live Mail, so that may not even be a good benchmark.

In conclusion, the new architecture of this browser really has me impressed. With each tab spawning its own process thread in Windows, gone are the days of having to close the entire browser because of one unruly website or plugin.

UPDATE
Based on Zeev’s suggestion below, I did attempt to load a list in datasheet view with Chrome. As expected, the ActiveX control is not available to display it properly as it is with Firefox. If you try it yourself, you will get this error:
The Standard View of your list is being displayed because your browser does not support running ActiveX controls.

Time will tell to see if Chrome becomes popular enough to be supported by Microsoft.