Chrome: all these cool little things!

I keep experimenting with Chrome,  Google’s neat new browser, ever since it appeared. Now when I use gmail, greader or gcalendar and happen to work on a windows PC I use Chrome instead of Firefox. I work on windows for office task, linux for development and mac for fun, in case you are interested.

Chrome is so much faster and I love the tab independence feature (i.e. when something ‘breaks’ in a tab, the rest keep working).
But I also keep using it  for the discovery experience it offers.
Chrome is minimal: not many toolbars, no separate search fields, no arcane menus for configuration. Yet, most of the goodies that we are used to from the other browsers, are there somehow. And more.

My latest discovery has to do with the in page search. Chrome has the seach box on top right and, as in firefox, it appears when a Ctrl+F is pressed.
Again, like firefox, typing a word in the search box highlights all the occurrences of the word in the page, something really convenient. But here Chrome offers something extra: it also highlights the position of the occurrences on the slider on the right. Take a look at the picture below:

I searched for the word “web” on the front page of this blog.In the picture you can see some of its occurences highligthed plus some orange lines on the slider on the right. These are the positions of the occurrences. So, once in a pretty large page,  you can slide quickly to the proper position!

It is these little details that make the difference from  “good” to “excellent”.

Google Chrome and Standards Compliance (updated)

A new kid is on the block: since Monday morning Google’s new browser, Chrome,  has been the most hot discussion topic on the internet. And, I guess, lots of people, all over the world,, are punching keys franticaly as we ‘speak’ , to test it.

Here is my contribution to the buzz.  How does the new browser behave in terms of standards compatibility? Let’s take the tests.

ACID2 gives

2008-09-03_0627

Which means 100% compatibility.

ACID3 gives :

2008-09-03_0630

which means 78% compliance. Were it 100% it should look  like this:

2008-09-03_0631

How do these results compare to the browsers on the market? I have run the same test on all the known browsers that pass the ACID2 test  and here are the results. All the test were run on a Windows XP with SP2.

Browser (version) ACID2 ACID3
IE (8.0.6001) 100% 12%
Firefox (3.0.1) 100% 71%
Safari (3.0.4) 100% 41%
Opera (9.52) 100% 83%
Chrome 100% 78%

So Chrome does a fairly good job in ACID3, but still trails Opera.

Update: I just spotted an article on CNET about Chrome’s standards compliance.Instead of comparing IE8 it compares IE7 on the Acid3 test and gives a result of 14% which I could not confirm.  The acid servers were very slow to respond but when they did I just got a 12% as in IE8.