Google Chrome is a web browser developed by Google that uses the WebKit layout engine. It was first released as a beta version for Microsoft Windows on September 2, 2008, and the public stable release was on December 11, 2008. The name is derived from the graphical user interface frame, or "chrome", of web browsers. As of July 2011, Chrome was the third most widely used browser with 22.14% worldwide usage share of web browsers, according to StatCounter.

In September 2008, Google released a large portion of Chrome's source code, including its V8 JavaScript engine, as an open source project entitled Chromium. This move enabled third-party developers to study the underlying source code and to help port the browser to the Mac OS X and Linux operating systems. Google also expressed hope that other browsers would adopt V8 to improve web application performance. The Google-authored portion of Chromium is released under the permissive BSD license, which allows portions to be incorporated into both open source and closed source software programs. Other portions of the source code are subject to a variety of open source licenses. Chromium implements a similar feature set as Chrome, but lacks built-in automatic updates, built-in PDF reader and Google branding, and most noticeably has a blue-colored logo in place of the multicolored Google logo.

History

For six years, Google's Chief Executive Eric Schmidt was against the idea of building an independent web browser. He stated that "At the time, Google was a small company", and he did not want to go through "bruising browser wars". However, after co-founders Sergey Brin and Larry Page hired several Mozilla Firefox developers and built a demonstration of Chrome, Mr. Schmidt admitted that "It was so good that it essentially forced me to change my mind".

Announcement

The release announcement was originally scheduled for September 3, 2008, and a comic by Scott McCloud was to be sent to journalists and bloggers explaining the features of and motivations for the new browser. Copies intended for Europe were shipped early and German blogger Philipp Lenssen of Google Blogoscoped made a scanned copy of the 38-page comic available on his website after receiving it on September 1, 2008. Google subsequently made the comic available on Google Books and mentioned it on their official blog along with an explanation for the early release.

Public release

The browser was first publicly released for Microsoft Windows (XP and later versions only) on September 2, 2008 in 43 languages, officially a beta version. Chrome quickly gained about 1% market share despite being only available for Microsoft Windows at that time. After the initial surge, usage share dropped until it hit a low of 0.69% in October 2008. It then started rising again and by December 2008, Chrome again passed the 1% threshold.

In early January 2009, CNET reported that Google planned to release versions of Chrome for Mac OS X and Linux in the first half of the year. The first official Chrome Mac OS X and Linux developer previews were announced on June 4, 2009 with a blog post saying they were missing many features and were intended for early feedback rather than general use.

In December 2009, Google released beta versions of Chrome for Mac OS X and Linux. Google Chrome 5.0, announced on May 25, 2010, was the first stable release to support all three platforms.

Chrome was one of the twelve browsers offered to European Economic Area users of Microsoft Windows in 2010.

Development

Chrome was assembled from 25 different code libraries from Google and third parties such as Mozilla's Netscape Portable Runtime, Network Security Services, NPAPI, as well as SQLite and a number of other open-source projects. The JavaScript virtual machine was considered a sufficiently important project to be split off (as was Adobe/Mozilla's Tamarin) and handled by a separate team in Denmark coordinated by Lars Bak at Aarhus. According to Google, existing implementations were designed "for small programs, where the performance and interactivity of the system weren't that important", but web applications such as Gmail "are using the web browser to the fullest when it comes to DOM manipulations and JavaScript", and therefore would significantly benefit from a JavaScript engine that could work faster.

(excluding IE) according to StatCounter]]

Chrome uses the WebKit rendering engine to display web pages, on advice from the Android team. Like most browsers, Chrome was extensively tested internally before release with unit testing, "automated user interface testing of scripted user actions", and fuzz testing, as well as WebKit's layout tests (99% of which Chrome is claimed to have passed). New browser builds are automatically tested against tens of thousands of commonly accessed websites inside the Google index within 20–30 minutes.

The Windows version of Chrome includes Gears, which adds features for web developers typically relating to the building of web applications (including offline support). However, Google is phasing out Gears in favor of HTML5.

In December 2010 Google announced that to make deploying Chrome easier in a business environment they would provide an official Chrome MSI package. The normal downloaded Chrome installer puts the browser in the user's home directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process. – it was formerly possible only when Chrome was installed using Google Pack. Google also created Group Policies to fine tune the behavior of Chrome in the business environment, for example setting automatic updates interval, a home page etc.

On January 11, 2011 the Chrome Product manager, Mike Jazayeri, announced that Chrome will no longer support H.264 video codec for its HTML 5 player, citing the desire to bring Google Chrome more inline with the currently available open codecs available in the Chromium project, which Chrome is based on.

Pre-releases

In addition to the stable build of Google Chrome, Google makes several pre-release versions, or "early release channels" available. These are referred to as channels because the browser is dynamically updated and are designated "Beta" "Dev" and "Canary". The Chrome Beta build is intended to be tested by anyone and is slightly newer than the stable version of chrome. The Dev, or developer build, is intended for users with software testing or programming experience. The Canary build is an automatically created version of the latest software from the parent Chromium project, which is not tested prior to release. As a result Google blocks the ability to set the Canary build as the user's default browser and allows it to be installed alongside another version of Chrome.

Chromium

While Chromium is the parent project of Google Chrome, there are some key differences that set the two apart. Chromium, unlike the pre-release versions of Chrome, is updated almost every day, but does not include the built-in Flash Player (it has to be downloaded separately) and Google Auto-updater found in Chrome. Chromium also has a less restrictive end user licence than the compiled builds of Chrome, and does not implement user RLZ tracking, a privacy concern.

Release history

Legend:

! Color	! Meaning
	Old release
	Current stable release
	Current beta release
	Current dev release

Major version	! Release date	!WebKit version	V8 JavaScript engine>V8 engine version	! Operating system support	! Significant changes
style="white-space:nowrap; background:salmon;"	0.2.149					First release.
		Improved plugin performance and reliability. Spell checking for input fields. Improved web proxy performance and reliability. Tab and window management updates.
		525	Bookmark manager with import and export support. Privacy section added to the application options. New blocked popup notification. Security fixes.
		528	First stable release.
		530	0.4	35% faster JavaScript on the SunSpider benchmark. Mouse wheel support. Full-screen mode. Full-page zoom. Form autofill. Sort bookmarks by title. Tab docking to browser and desktop edges. Basic Greasemonkey support.
		532	1.2	New "new tab" page for improved customization. 25% faster JavaScript. HTML5 video and audio tag support. Lightweight theming.
				Extensions. Bookmark synchronization. Enhanced developer tools. Improved HTML5 support. Performance improvements. Full ACID3 pass. HTTP byte range support. Increased security. Experimental new anti-reflected-XSS feature called "XSS Auditor".
		Translate infobar. New privacy features. Disabled XSS Auditor.
			533		2.1	rowspan="11" style="text-align:center;"	WindowsMacLinux		W3C Geolocation API>Geolocation APIs, App Cache, web sockets, and file drag-and-drop). Revamped bookmark manager. Adobe Flash Player integrated.
style="white-space:nowrap; background:salmon;"	6.0.472		534.3	2.2	Updated and more streamlined UI with simplified Omnibox. New tab page. Merged menu buttons. Form Autofill. Expanded synchronization support to include extensions and Autofill data. Support for WebM videos. Improvements for performance and stability. Built-in PDF support (disabled by default).
		534.7	2.3.11.22
			534.10		2.4.9.19		This release added "about:flags" to showcase experimental features such as Chrome Instant, side tabs on Windows, Tabbed Settings, Click to Play, background web applications, Remoting, Disable outdated plug-ins, XSS Auditor, Cloud Print Proxy, GPU Accelerated Compositing, WebGL support for the Canvas element, and a "Tab Overview" mode (like Exposé (Mac OS X)>Exposé) for Mac OS.
style="white-space:nowrap; background:salmon;"	9.0.597			534.13		2.5.9.6		WebGL enabled by default. Adobe Flash sandboxing on Windows and Chrome Instant (à la Google Instant) option. WebP support. New flags: Print Preview, GPU Accelerated Compositing, GPU Accelerated Canvas 2D, Google Native Client, CRX-less Web Apps, Web Page Prerendering, Experimental Extension APIs, Disable hyperlink auditing.
style="white-space:nowrap; background:salmon;"	10.0.648			534.16		3.0.12.30		Google Cloud Print sign-in interface enabled by default. Partially implemented sandboxing of the GPU process. Faster JavaScript performance due to incorporation of V8 (JavaScript engine)#Crankshaft>Crankshaft, an improved compiler for V8. Settings pages that open in a tab, rather than a dialog box. Malware reporting and disabling outdated plugins. Password sync added to Chrome Sync and enabled by default. GPU Accelerated Video. Background WebApps. webNavigation extension API.
style="white-space:nowrap; background:salmon;"	11.0.696			534.24		3.1.8.16		HTML5 Speech Input API. Updated icon.
style="white-space:nowrap; background:salmon;"	12.0.742			534.30		3.2.10.21		Hardware accelerated 3D CSS. New Safe Browsing protection against downloading malicious files. Ability to delete Flash cookies from inside Chrome. Launch Apps by name from the Omnibox. Integrated Sync into new settings pages. Improved screen reader support. New warning when hitting Command-Q on Mac. New flags: P2P API. Existing tab on foreground on open. Experimental new tab page. Add grouping to tab context menu. Run PPAPI Flash in the renderer process. Multiple Profiles. Removed Google Gears. Print and Save buttons in the PDF viewer.
style="white-space:nowrap; background:#a0e75a;"	13.0.782			535.1		3.3.10.30		Instant Pages (pre-rendering of webpages). Native print interface and preview (Linux and Windows only). New chrome://flags experiments: Experimental new tab page, Restrict Instant To Search.
style="white-space:nowrap; background:lightblue;"	14.0.835			535.1		3.4.14.17		Native Client (NaCl) enabled for apps in the Chrome Web Store. Web Audio API. Additional Mac OS X Lion feature support. Sync Encryption for all data. Print Preview on Mac. Experimental Web Request extension API. Experimental Content Settings extension API. HTTPS over DNSSEC.
style="white-space:nowrap; background:#d6b4f1;"	15.0.865			535.2		3.5.8		Faster print preview. Removed chrome://flags experiments: Experimental new tab page. Experimental new tab page on by default. Switched to FFmpeg native VP8 decoder.

Note: Old development builds are not shown here after they go through beta and become stable releases.

Features

Google Chrome aims to be secure, fast, simple and stable. There are extensive differences from its peers in Chrome's minimalistic user interface, which is atypical of modern web browsers. For example, Chrome does not render RSS feeds. Chrome's strength is its application performance and JavaScript processing speed, both of which were independently verified by multiple websites to be the swiftest among the major browsers of its time. Many of Chrome's unique features had been previously announced by other browser developers, but Google was the first to implement and publicly release them. For example, its most prominent graphical user interface (GUI) innovation, the merging of the address bar and search bar (the Omnibox), was first announced by Mozilla in May 2008 as a planned feature for Firefox. Such a feature was already implemented in Konqueror in 2004.

Acid tests

test on Google Chrome 4.0]]

The first release of Google Chrome passed both the Acid1 and Acid2 tests. Beginning with version 4.0, Chrome passed all aspects of the Acid3 test.

Web standards conformance tests

On Ecma International's ECMAScript standards conformance Test 262 (version 0.7.5.3), Chrome version 13.0.782.215 scores 483/10927. The beta version, 14.0.835.109, scored 420/10927. The dev version, 15.0.861.0, scores 411/10927. Lower scores are better, as the figure represents the number of failed tests out of the total number of tests.

On the official CSS 2.1 test suite by standardization organization W3C, Webkit, the Chrome rendering engine, passes 89.75% (89.38% out of 99.59%) of covered CSS 2.1 tests.

Security

Chrome periodically retrieves updates of two blacklists (one for phishing and one for malware), and warns users when they attempt to visit a harmful site. This service is also made available for use by others via a free public API called "Google Safe Browsing API". Google notifies the owners of listed sites who may not be aware of the presence of the harmful software.

Chrome will typically allocate each tab to fit into its own process to "prevent malware from installing itself" and prevent what happens in one tab from affecting what happens in another; however, the actual process-allocation model is more complex. Following the principle of least privilege, each process is stripped of its rights and can compute, but cannot write files or read from sensitive areas (e.g. documents, desktop)—this is similar to the "Protected Mode" used by Internet Explorer on Windows Vista and Windows 7. The Sandbox Team is said to have "taken this existing process boundary and made it into a jail"; for example, malicious software running in one tab is supposed to be unable to sniff credit card numbers entered in another tab, interact with mouse inputs, or tell Windows to "run an executable on start-up" and it will be terminated when the tab is closed. This enforces a simple computer security model whereby there are two levels of multilevel security (user and sandbox) and the sandbox can only respond to communication requests initiated by the user. On Linux sandboxing uses the seccomp mode.

Typically, plugins such as Adobe Flash Player are not standardized and as such, cannot be sandboxed as tabs can be. These often must run at, or above, the security level of the browser itself. To reduce exposure to attack, plugins are run in separate processes that communicate with the renderer, itself operating at "very low privileges" in dedicated per-tab processes. Plugins will need to be modified to operate within this software architecture while following the principle of least privilege. Chrome supports the Netscape Plugin Application Programming Interface (NPAPI), but does not support the embedding of ActiveX controls. On March 30, 2010 Google announced that the latest development version of Chrome would include Adobe Flash as part of the browser, eliminating the need to download and install it separately. Flash would be kept up to date as part of Chrome's own updates. Java applet support is available in Chrome with Java 6 update 12 and above. Support for Java under Mac OS X was provided by a Java Update released on May 18, 2010.

A private browsing feature called Incognito mode is provided that prevents the browser from storing any history information or cookies from the websites visited. Incognito mode is similar to the private browsing feature in Internet Explorer 8 (and up), Mozilla Firefox 3.5 (and up), Opera 10.5 (and up) and Safari.

Security vulnerabilities

On January 12, 2011 versions of Chrome prior to version 8.0.552.237 were identified by US-CERT as "contain[ing] multiple memory corruption vulnerabilities...By convincing a user to view a specially crafted HTML document, PDF file, or video file, an attacker can cause the application to crash or possibly execute arbitrary code." The vulnerability was subsequently patched and a new stable version was released to the public with Chrome's auto-update mechanism.

No security vulnerabilities in Chrome have been successfully exploited in three years of Pwn2Own.

Malware blocking

Statistics show that users are four times more likely to be tricked into downloading malware than be compromised by an exploit. In a recent study, Chrome 10 blocked only 13% of malicious URLS, tied for third place with Safari and Firefox. In contrast, Internet Explorer 9 blocked 92% of malware with its URL-based filtering, and 100% with application-based filtering enabled. Internet Explorer 8, in second place, blocked 90% of malware. Exploits that install malware without the user being aware (also referred to as "clickjacking" and "drive-by downloads") were not included in this particular study.

Speed

The JavaScript virtual machine used by Chrome, the V8 JavaScript engine, has features such as dynamic code generation, hidden class transitions, and precise garbage collection. Tests by Google in September 2008 showed that V8 was about twice as fast as Firefox 3.0 and the WebKit nightlies.

Several websites performed benchmark tests using the SunSpider JavaScript Benchmark tool as well as Google's own set of computationally intense benchmarks, which include ray tracing and constraint solving. They unanimously reported that Chrome performed much faster than all competitors against which it had been tested, including Safari (for Windows), Firefox 3.0, Internet Explorer 7, Opera, and Internet Explorer 8. However in more recent independent tests of JavaScript performance, Chrome has been scoring just behind Opera's Presto engine since it was updated in version 10.5.

On September 3, 2008, Mozilla responded by stating that their own TraceMonkey JavaScript engine (then in beta), was faster than Chrome's V8 engine in some tests. John Resig, Mozilla's JavaScript evangelist, further commented on the performance of different browsers on Google's own suite, commenting on Chrome's "decimating" (sic) of the other browsers, but he questioned whether Google's suite was representative of real programs. He stated that Firefox 3.0 performed poorly on recursion intensive benchmarks, such as those of Google, because the Mozilla team had not implemented recursion-tracing yet.

Two weeks after Chrome's launch, the WebKit team announced a new JavaScript engine, SquirrelFish Extreme, citing a 36% speed improvement over Chrome's V8 engine.

Chrome uses DNS prefetching to speed up website lookups, as do Firefox and Safari. This feature is available in Internet Explorer as an extension, and in Opera as a UserScript.

Chrome utilizes the faster SPDY protocol designed to replace HTTP when communicating with Google services, such as Google Search, Gmail, Chrome sync and when serving Google's ads. Google acknowledges that the use of SPDY is enabled in the communication between Chrome and Google's SSL-enabled servers.

Stability

The Gears team implemented a multi-process architecture in Chrome where, by default, a separate process is allocated to each site instance and plugin, a procedure referred to as process isolation. This prevents tasks from interfering with each other, increasing security and stability. An attacker successfully gaining access to one application cannot gain access to others, and failure in one instance results in a Sad Tab screen of death, similar to the well-known Sad Mac, but only a single tab crashes instead of the whole application. This strategy exacts a fixed per-process cost up front, but results in less memory bloat overall as fragmentation is confined to each instance and no longer requires further memory allocations. Safari and Firefox are also adopting this architecture in upcoming versions, meaning that most common browsers will use a multi-process architecture in the near future.

Chrome includes a process management utility called Task Manager which allows the user to see what sites and plugins are using the most memory, downloading the most bytes and over-utilizing the CPU and provides the ability to terminate them.

User interface

By default, the main user interface includes back, forward, refresh/cancel and menu buttons. A home button is not shown by default, but can be added through the preferences menu to take the user to the new tab page or a custom home page.

Tabs are the primary component of Chrome's user interface and as such, have been moved to the top of the window rather than below the controls. This subtle change contrasts with many existing tabbed browsers which are based on windows and contain tabs. Tabs (including their state) can be transferred seamlessly between window containers by dragging. Each tab has its own set of controls, including the Omnibox.

The Omnibox is the URL box at the top of each tab, which combines the functionality of both the Address bar and search box. If a user enters the URL of a site previously searched from, Chrome allows pressing Tab to search the site again directly from the Omnibox. When a user starts typing in the Omnibox, Chrome provides suggestions for previously visited sites (based on the URL or in-page text), popular websites (not necessarily visited before – powered by Google Suggest), and popular searches. Although Google Suggest can be turned off, suggestions based on previously visited sites cannot be turned off. Chrome will also autocomplete the URLs of sites visited often. If a user types several keywords into the Omnibox and press enter, Chrome will conduct the search using the default search engine.

When Google Chrome is not maximized, the tab bar appears directly under the title bar. When maximized, the tabs become flush with the top of the titlebar. Like other browsers, it has a full-screen mode that hides the operating system's interface as well as the browser chrome.

One of Chrome's differentiating features is the New Tab Page, which can replace the browser home page and is displayed when a new tab is created. Originally, this showed thumbnails of the nine most visited web sites, along with frequent searches, recent bookmarks, and recently closed tabs; similar to Internet Explorer and Firefox with Google Toolbar 6, or Opera's Speed Dial. In Google Chrome 2.0, the New Tab Page was updated to allow users to hide thumbnails they did not want to appear. Starting in version 3.0, the New Tab Page was revamped to display thumbnails of the eight most visited web sites. The thumbnails could be rearranged, pinned, and removed. Alternatively, a list of text links could be displayed instead of thumbnails. It also features a "Recently closed" bar that shows recently closed tabs and a "tips" section that displays hints and tricks for using the browser.

Chrome includes a bookmark manager that can be opened from a menu. Adding the command-line option: --bookmark-menu adds a bookmarks button to the right of the Omnibox that can be used in place of the bookmarks bar. However, this functionality is currently unavailable on the Linux and Mac platforms.

Popup windows are associated with the tab they came from and will not appear outside the tab unless the user explicitly drags them out.

Google Chrome's preferences window has three tabs: Basic, Personal Stuff, and Under the Hood. The Basic tab includes options for the home page, search engine, and default browser. The Personal Stuff tab lets users configure synchronization, saved passwords, form autofill, browsing data, and themes. The Under the Hood tab allows changing network, privacy, download, and security settings.

Chrome does not have a status bar, but displays loading activity and hover-over information via a status bubble that pops up at the bottom left of the relevant page, excluding hovering over links in image maps.

For web developers, Chrome features an element inspector similar to the one in Firebug.

As part of Google's April Fools' Day jokes, a special build of Chrome was released on April 1, 2009 with the additional feature of being able to render pages in anaglyph 3D.

Chrome has special URLs that load application-specific pages instead of websites or files on disk. Chrome also has a built-in capability to enable experimental features. Originally called about:labs, the address was changed to about:flags to make it less obvious to casual users.

In March 2011, Google introduced a new simplified logo to replace the previous 3D logo that had been used since the project's inception. Google designer Steve Rura explained the company reasoning for the change, "Since Chrome is all about making your web experience as easy and clutter-free as possible, we refreshed the Chrome icon to better represent these sentiments. A simpler icon embodies the Chrome spirit – to make the web quicker, lighter, and easier for all."

Desktop shortcuts and apps

Chrome allows users to make local desktop shortcuts that open web applications in the browser. The browser, when opened in this way, contains none of the regular interface except for the title bar, so as not to "interrupt anything the user is trying to do." This allows web applications to run alongside local software (similar to Mozilla Prism and Fluid).

This feature, according to Google, will be enhanced with the Chrome Web Store, a one-stop web-based web applications directory which opened in December 2010.

Chrome Web Store

Announced on December 7, 2010, the Chrome Web Store allows users to install web applications as extensions to the browser, although these function simply as links to popular web pages and/or games. The themes and extensions have also been tightly integrated into the new store, allowing users to search the entire catalog of Chrome extras.

Criticism of the idea came quickly. Ryan Paul of Ars Technica wrote on December 9, 2010: "The way that users consume applications in the desktop and mobile world is fundamentally different than they (sic) way that they do it on the Web—where paywalls are often reviled and there is little distinction between content and software. In such an environment, does the application store model make any sense? We are not convinced...Aside from gaming, the idea of an application store in a Web browser—where installation is little more than bookmarking—seems counterintuitive and leaves us with the impression that the entire exercise is a solution in search of a problem."

The Chrome Web Store was opened on February 11, 2011 with the stable, non-beta, release of Google Chrome 9.0.597.98.

Aero peek capability

Google has included aero peek capability for each tab on Windows 7. This has not been added by default but can be user enabled, resulting in a displayed thumbnail image of the tab. This will create similar functioning to that which is already included in IE8, Firefox and other browsers.

Negative responses from beta users on the inefficiency of aero peek tabs implementation in Chrome lead Google to exclude this as a default function.

Extensions

On September 9, 2009, Google enabled extensions by default on Chrome's Dev channel, and provided several sample extensions for testing. In December, the Google Chrome extension gallery beta began with over 300 extensions.

Along with Google Chrome 4.0, the extension gallery was officially launched on January 25, 2010, containing over 1500 extensions.

Google became leaders in the field of Search engine optimization and have even published an SEO Starter Guide which provides valuable information on how to optimize your site in the Google era. Matt Cutts who works for the Search Quality group in Google, specializing in search engine optimization issues, is well known in the SEO community for enforcing the Google Webmaster Guidelines and advising the public on how to get better website visibility in Google. Thanks to Google's cooperation with the SEO industry, Google Chrome became a valuable browser for developers in the SEO business who developed many SEO extensions for Google Chrome, Chrome web store also enables many SEO tools.

As of February 4, 2011, the extension gallery featured over 11500 extensions, including official extensions from The Independent, CEOP, Transport for London, Cricinfo, WOT: Web of Trust and FIFA.

Themes

Starting with Google Chrome 3.0, users can install themes to alter the appearance of the browser. Many free third-party themes are provided in an online gallery, accessible through a "Get themes" button in Chrome's options.

Automatic web page translation

Starting with Google Chrome 4.1 the application added a built-in translation bar using Google Translate. Translation is currently available for 52 languages.

Release channels and updates

On January 8, 2009 Google introduced a new release system with three distinct channels: Stable, Beta, and Developer preview (called the "Dev" channel). Before this change there were only two channels: Beta and Developer preview. All previous Developer channel users were moved to the Beta channel. The reason given by Google is that the Developer channel builds are less stable and polished than those that Developer channel users were getting during Google Chrome's Beta period. The stable channel will be updated with features and fixes once they have been thoroughly tested in the Beta channel, and the Beta channel will be updated roughly monthly with stable and complete features from the Developer channel. The Developer channel is where ideas get tested (and sometimes fail) and can be very unstable at times. On July 22, 2010 Google announced it will ramp up the speed it will release new stable versions; they will shorten the release cycles from quarterly to 6 weeks. The faster release cycle brought a fourth channel: the "Canary" release; the name refers to using canaries in coal mines, so if a change "kills" Chrome Canary, they will block it from the developer build. Canary will be "the most bleeding-edge official version of Chrome and somewhat of a mix between Chrome dev and the Chromium snapshot builds". Canary releases run side-by-side with any other channel; it is not linked to the other Google Chrome installation and can therefore run different synchronization profiles, themes, and browser preferences. It cannot be set as the default browser. Canary was Windows-only at first, a Mac OS X version was released on May 3, 2011.

Chrome automatically keeps itself up to date. The details differ by platform. On Windows, it uses Google Updater, and autoupdate can be controlled via Group Policy, or users can download a standalone version that does not autoupdate. On Mac, it uses Google Update Service, and autoupdate can be controlled via the Mac OS X "defaults" system. On Linux, it lets the system's normal package management system supply the updates.

Google uses its Courgette algorithm to provide the binary difference of the user's current version in relation to the new version that's about to be automatically updated to. These tiny updates are well suited to minor security fixes and allow Google to push new versions of Chrome to users quickly, thereby reducing the window of vulnerability of newly discovered security flaws.

Usage tracking

Chrome sends details about its usage to Google through both optional and non-optional user tracking mechanisms.

+ Tracking methods	! Method	! Information sent	! When	! Optional?
	Randomly generated token included in installer. Used to measure success rate of Google Chrome.		On installation
			* On Google search query	* On first launch and first use of address bar
	Unique identifier along with logs of usage metrics and crashes.
	Text typed into the address bar	While typing
	Text typed into the address bar	Upon receiving "Server not found" response
	Details about crashes and failures
	Details about Chrome version

Some of the tracking mechanisms can be optionally enabled and disabled through the installation interface and through the browser's options dialog. Unofficial builds, such as SRWare Iron and ChromePlus, seek to remove these features from the browser altogether. The RLZ feature is not included in the Chromium browser either.

In March 2010, Google devised a new method to collect installation statistics: the unique ID token included with Chrome is now only used for the first connection that Google Update makes to its server. This sole remaining non-optional user tracking mechanism is removed following the server ping.

System requirements

The recommended requirements for optimal performance of Chrome are:

Windows: XP Service Pack 2+ / Vista / 7, Intel Pentium 4 or later, 100MB Hard Disk, 128MB memory

Mac OS X: 10.5.6 or later, Intel (not PPC), 100MB Hard Disk, 128MB memory

Linux: Ubuntu 8.04 or later / Debian 5 / OpenSuse 11.1 / Fedora Linux 10, Intel Pentium 3 / Athlon 64 or later, 100MB Hard Disk, 128MB memory

64-bit builds

As of 2011, 64-bit builds are available for Linux, with only 32-bit available for Mac OS X and Windows.

Reception

according to Stat Counter, Chrome was 22.14% in July 2011.]] In 2008, The Daily Telegraph's Matthew Moore summarizes the verdict of early reviewers: "Google Chrome is attractive, fast and has some impressive new features, but may not—yet—be a threat to its Microsoft rival."

Initially, Microsoft reportedly "played down the threat from Chrome" and "predicted that most people will embrace Internet Explorer 8." Opera Software said that "Chrome will strengthen the Web as the biggest application platform in the world." But by February 25, 2010, BusinessWeek had reported that "For the first time in years, energy and resources are being poured into browsers, the ubiquitous programs for accessing content on the Web. Credit for this trend—a boon to consumers—goes to two parties. The first is Google, whose big plans for the Chrome browser have shaken Microsoft out of its competitive torpor and forced the software giant to pay fresh attention to its own browser, Internet Explorer. Microsoft all but ceased efforts to enhance IE after it triumphed in the last browser war, sending Netscape to its doom. Now it's back in gear." Mozilla said that Chrome's introduction into the web browser market comes as "no real surprise", that "Chrome is not aimed at competing with Firefox", and furthermore that it should not affect Google's revenue relationship with Mozilla.

}}

According to StatCounter, Chrome was the most used web browser in Argentina, Chile, Uruguay, Philippines, Malaysia, Pakistan, Mauritania, Tunisia, Albania, Macedonia, Moldova and Armenia in July 2011.

Criticism

User tracking

Concern about Chrome's optional usage collection and tracking have been noted in several publications. On September 2, 2008, a CNET news item drew attention to a passage in the Terms of Service statement for the initial beta release, which seemed to grant to Google a license to all content transferred via the Chrome browser. The passage in question was inherited from the general Google terms of service. On the same day, Google responded to this criticism by stating that the language used was borrowed from other products, and removed the passage in question from the Terms of Service. Google noted that this change would "apply retroactively to all users who have downloaded Google Chrome." There was subsequent concern and confusion about whether and what information the program communicates back to Google. The company stated that usage metrics are only sent when users opt in by checking the option "help make Google Chrome better by automatically sending usage statistics and crash reports to Google" when the browser is installed.

The optional suggestion service included in Google Chrome has been criticized because it provides the information typed into the Omnibox to the search provider before the user even hits return. This allows the search engine to provide URL suggestions, but also provides them with web usage information tied to an IP address. The feature can be selected off in the preferences-under the hood-privacy box.

Do Not Track

In April 2011, Google was criticized for not signing onto the Do Not Track feature for Chrome that is being incorporated in most other modern web browsers, including Firefox, Internet Explorer, Safari, and Opera. Critics pointed out that a new patent Google was granted in April 2011, for greatly enhanced user tracking though web advertising, will provide much more detailed information on user behavior and that do not track will hurt Google's ability to exploit this. Software reviewer Kurt Bakke of Conceivably Tech wrote, "Google said that it intends charge advertisers based on click-through rates, certain user activities and a pay-for-performance model. The entire patent seems to fit Google's recent claims that Chrome is critical for Google to maintain search dominance through its Chrome web browser and Chrome OS and was described as a tool to lock users to Google's search engine and – ultimately – its advertising services. So, how likely is it that Google will follow the do-not-track trend? Not very likely." Mozilla developer Asa Dotzler noted, "It seems pretty obvious to me that the Chrome team is bowing to pressure from Google's advertising business and that's a real shame. I had hoped they'd demonstrate a bit more independence than that."

Google argued that the technology is useless at the present time, as advertisers are not required to obey the user's tracking preference and as it is still unclear on what constitutes tracking (as opposed to storing statistical data or user preferences). As an alternative, Google offers an extension called "Keep My Opt-Outs", which permanently bars ad companies from installing cookies on the user's computer.

The reaction to this extension was mixed. Paul Thurrott of Windows IT Pro called the extension "much, much closer to what I've been asking for—i.e. something that just works and doesn't require the user to figure anything out—than the IE or Firefox solutions" while lamenting the fact that the extension is not included as part of the browser itself.

See also

Browser wars

Chromium (web browser)

Comparison of web browsers

Google Chrome Frame

Google Chrome OS

List of web browsers

SRWare Iron

Timeline of web browsers

Usage share of web browsers

Notes

References

External links

Google Chrome offline installer

Google Chrome Feature List

Google Chrome official blog

Chromium project page at Google Code

The Chromium blog from Google

Google Chrome Comic Book

Category:2008 software Category:C++ software Category:Cloud clients Category:Free web browsers Category:Google software Category:Windows web browsers Category:Software based on Webkit Category:Site-specific browsing Category:Portable software Category:Mac OS X web browsers

af:Google Chrome ar:جوجل كروم bn:ক্রোম be-x-old:Google Chrome bg:Google Chrome ca:Google Chrome cs:Google Chrome da:Google Chrome de:Google Chrome et:Google Chrome es:Google Chrome eo:Google Chrome eu:Google Chrome fa:گوگل کروم fr:Google Chrome gu:ગૂગલ ક્રોમ ko:구글 크롬 hy:Գուգլ Քրոմ hi:गूगल क्रोम hsb:Google Chrome hr:Google Chrome id:Google Chrome os:Google Chrome is:Google Chrome it:Google Chrome he:גוגל כרום kn:ಗೂಗಲ್‌ ಕ್ರೋಮ್‌ ಬ್ರೌಸರ್ krc:Google Chrome ka:Google Chrome kk:Google Chrome ht:Google chrome lv:Google Chrome lt:Google Chrome li:Google Chrome hu:Google Chrome mk:Google Chrome ml:ഗൂഗിൾ ക്രോം mr:गूगल क्रोम ms:Google Chrome my:ဂူဂယ် ခရုမ်း nl:Google Chrome ja:Google Chrome no:Google Chrome nn:Google Chrome oc:Google Chrome uz:Google Chrome pl:Google Chrome pt:Google Chrome ro:Google Chrome ru:Google Chrome sq:Google Chrome simple:Google Chrome sk:Google Chrome sl:Google Chrome sr:Гугл кроум fi:Google Chrome sv:Google Chrome ta:கூகிள் குரோம் tt:Google Chrome te:గూగుల్ క్రోమ్ th:กูเกิล โครม tr:Google Chrome uk:Google Chrome ur:گوگل کروم vi:Google Chrome wuu:谷歌铬美 zh-yue:Google Chrome zh:Google Chrome