Google Chrome

Hey Jun,

Just a quick word - Aikiweb mostly looks fine in Chrome, but the forums menus look different (no pull-down sub-menus).

Best,
Daniel

Well, still in beta, so...

Tried it and not impressed. I'm running the beta of IE8 and it doesn't bog down my system like Chrome and v3 of Firefox. Found this article interesting as I've experienced these issues with FF.

http://apnews.excite.com/article/200...D92V15G80.html

of course, you mileage may vary.

As far as I can tell it is very fast and works well. I'm impressed with what they have so far. I'll be more impressed when it builds on my computer (tried compiling and it failed on windows and mac).

As far as replacing my browser, I don't see it happening in the short term. I need extentions (adblock, noscript, firebug (it does have something similar built in), greasemonkey, google notebook (odd huh?), stumbleupon, foxmarks, etc). Until it supports some kind of extension framework I don't see me using it.

Rendering it uses the same engine as Safari. Which gives me a good feeling all around. I love safaris rendering engine. So far all my code works perfectly on it. I did find my sites worked a lot faster on chrome then on firefox. Hopefully firefox will improve because of this or chrome will get a mac/linux client and allow for extensions (and develop a community)

Hi Daniel,

I'll see about taking a look at the forum using Chrome when I get the chance. Thanks for the heads-up.

Best,

-- Jun

Ehhh...Chrome needs more polish.

I have been an Opera user for years. http://www.opera.com

Aikiweb looks very sexy in Opera.

William Hazen

Don Magee wrote: So far all my code works perfectly on it. I did find my sites worked a lot faster on chrome then on firefox.

I found the same with my code. However, some other people's code doesn't work right. I'm personally wondering how Chrome is identifying itself to servers... so much code nowadays requires workarounds for certain browsers, so if it's ending up on the end of an IF-ELSEIF-ELSE conditional statement, some more 'complex' sites could just be stripping away features (so far I've noticed that eBay seem to have such a system in place, although without viewing their source code I can't be 100% sure).

Can't wait for a Release Candidate and Linux build.

David Maidment wrote: I found the same with my code. However, some other people's code doesn't work right. I'm personally wondering how Chrome is identifying itself to servers... so much code nowadays requires workarounds for certain browsers, so if it's ending up on the end of an IF-ELSEIF-ELSE conditional statement, some more 'complex' sites could just be stripping away features (so far I've noticed that eBay seem to have such a system in place, although without viewing their source code I can't be 100% sure). Can't wait for a Release Candidate and Linux build.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.X.Y.Z Safari/525.13.

I use jquery for most of my scripts and fall though css, so I've never ran into the browser detection horrors. Most people should treat chrome as safari.

That's interesting then... Safari's usually been fairly good to me in terms of browser-specific features. I note also that Chrome seems to be scoring very well in the Acid tests. Worth keeping an eye on.