- More porn sneaks onto the iPhone
- 'Swatting' case shows need to ban caller-ID spoofing
- Why the iPhone can't be "killed"
- Nortel enterprise chief wants to bring back Bay
- US sets final emergency responder wireless pilot
|
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 businessBy google business on June 29, 2009, 3:37 amIt is a great filling of working with Google and milestones are always a good time for introspection. Interesting, fun, surprising, insightful, inspiring, impactful,...
Reply | Read entire comment
WHY doesnt Google fix the probem themselves?By Alet on January 30, 2009, 2:42 pmWhy must we search for a fix on the Chrome / Flashplayer problem? Can Google not fix the problem themselves? Why did you make Chrome available for downloading without...
Reply | Read entire comment
Chrome problem with Adobe FlashplayerBy Alet on January 30, 2009, 2:34 pmIs there ANY person who can tell me how to fix the problem with Chrome and Flashplayer?? I wish I could completely get rid of Chrome from my laptop but CANNOT! HELP...
Reply | Read entire comment
bookmark links as well as on home pageBy imma on September 17, 2008, 6:10 amthey are available, just defaulting to hidden as they take up space try ctrl-b to switch them on/off
Reply | Read entire comment
Java != Javascript.By Anon on September 14, 2008, 7:09 amJava != Javascript.
Reply | Read entire comment
View all comments