Google Chrome
September 3rd, 2008 | Published in General | 5 Comments
The buzz on the web is all about the new Google browser — Google Chrome. So naturally, as web developers we had to give it a try and see how fast it really is. And you know what? its lightenning fast. Not a surprise given that it is powered by WebKit!There are few other things that are very exciting about Google Chrome but then there are also few things that we didn’t like. Things we didn’t like:1. The name. I mean what the heck were they thinking!?2. The completely minimized theme. While it is great from my perspective, I think the general public would’ve liked it better if they could find it familiar to use. From UI prespective, it is very important to bring the familiarity factor in for the user. They should be able to look at it and identify it as a browser something that looks like IE but works better. So have you given it a run yet? What do you think?
September 3rd, 2008 at 9:52 am (#)
should be interesting to see if Chrome works more efficiently than FireFox… if it’s faster than Firefox, since isn’t IE, then i’ll use it
September 5th, 2008 at 1:22 am (#)
about the name:
it’s great, it’s short - it has not much of a previous meaning and we will get used to it (remember how many people did not accept the firebird name, and when firefox was introduced they wanted firebird back….)
ad 2) google tries a new paradigm with the browser: it’s not any more about the browser - it’s about the web, so i think it was a great choice to get rid of all the stuff (even so i made sure that ma beloved bookmarks toolbar is shown).
September 15th, 2008 at 12:38 am (#)
did you realize that the refelction.js (like the fork used in protolfow) does not work with google chrome, do you allready have a fix for it? asks and br face search
September 18th, 2008 at 4:06 am (#)
@raid
to et the reflection work at protoflow V1 use
cahnge the webkit exception at the relfection.js
if (navigator.appVersion.indexOf(’WebKit’) != -1 && navigator.appVersion.indexOf(’Chrome’) == -1) {
context.fill();
} else {
context.fillRect(0, 0, reflectionWidth, reflectionHeight*2);
}
somewhere around line 139
it’s not a perfect patch because there are issues that at first the background of the reflection is white, but better then no reflection
br
franz
http://www.facesaerch.com
September 18th, 2008 at 4:38 am (#)
^ Thanks Franz.
I will update the code tonight and publish it on the site.