- Microsoft Windows chief decries standards grandstanding
- The 5 best, and 5 worst, features of Google Chrome OS
- Federal government using PS3 to crack pedophile passwords
- 10G Ethernet cheat sheet
- Top 10 free Windows tools for IT pros, at a glance
|
The recent introduction of the Google Chrome browser wildly succeeded in setting the Web abuzz. Web digest after Web digest regurgitates the main points about the obvious user interface features and the cute corroborating comic, but is there more? The answer is yes, a bit of which — like it's foundation and some user-facing features — has already been around the browser world for quite awhile. But others, like several network-focused measures, will serve to be notable advances. See Powell's follow up: The Google Chrome conspiracy theories The most important point about Chrome that has been widely mentioned — even if the implications of which are often glossed over — is that Chrome is based upon WebKit. What this means is that Chrome does whatever the particular build of WebKit it is derived from does (at this point build 525.13). For example, while the current build of WebKit passes Acid3 perfectly, the current build of Chrome does not since it is built on an older version of the WebKit rendering engine. |
|
|
This will obviously get rectified when Google pulls the new WebKit code into a future version but, for now at least, Chrome can't claim the king-of-the-hill mark in terms standards compliance. Numerous other complaints about Chrome's rendering quirks, bugs in the CSS text-shadow property, and alternate style sheet problems were registered by Web designers in a matter of hours after the launch, but it is likely a great number of these issues are due to the older WebKit build, as opposed to Chrome-specific concerns. However, it would be unwise to brush aside the WebKit engine inclusion too quickly as it presents more problematic issues as well. In particular, the drive-by download problem dubbed "carpet-bombing" that plagued some Safari versions a while back is currently alive and well in Chrome. In short, this is Beta software and should be treated as such from a security standpoint especially: avoid doing your beta testing on sites with a high potential for malicious intent. There are many noticeable user features about Google Chrome, some subtle some not so. The top tabs are one of the things that were nice to use. |
|
|
When making a new tab the special start page that presents an Opera-like "speed dial" feature is also new and improved from other implementations with bookmark and recently-closed tabs links. |
|
Comments (21)
Google Chrome: Is there anything under the hood?By Google Subnet on September 6, 2008, 3:19 amWe want to hear from YOU! Have you had a chance to take Chrome for a test drive? Does it live up to all the browser buzz and hype? Should Microsoft or Mozilla be...
Reply | Read entire comment
I find Chrome to be slow onBy Anon on September 9, 2008, 12:11 pmI find Chrome to be slow on loading pages.
Reply | Read entire comment
I hate the way bookmarks are handledBy Dest on September 9, 2008, 12:12 pmThat is about my only complaint about Chrome. They should put a link icon in the browser for bookmarks and not try to link everything to the home page. If...
Reply | Read entire comment
This browser is no good.By Anon on September 9, 2008, 12:12 pmThis browser is no good. Doesn't support java and other web technologies. Firefox is still the best.
Reply | Read entire comment
Very Cool, but it's a Crash-O-Matic of a BetaBy Anon on September 9, 2008, 12:15 pmThey are going to have to find a way to plug the bomb hole and to secure the archive files.
Reply | Read entire comment
google chrome (Don Safar)By Anon on September 9, 2008, 12:15 pmA number of the websites that I use everyday in my work are unworkable in chrome. These include internal and external websites that work in IE and Firefox. I'll...
Reply | Read entire comment
View all comments