Jump to content

Google Chrome

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 90.199.49.140 (talk) at 11:51, 18 April 2011 (→Release history). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This article is about the web browser. For the operating system, see Google Chrome OS.
Google Chrome
Developer(s)Google Inc.
Initial releaseSeptember 2, 2008; 16 years ago (2008-09-02)
Stable release
Windows, macOS, Linux131.0.6778.204/205[1] Edit this on Wikidata / 18 December 2024; 9 days ago (18 December 2024)
Windows Server 2012/2012 R2109.0.5414.165[2] / 13 September 2023; 15 months ago (2023-09-13)
Android131.0.6778.200[3] Edit this on Wikidata / 18 December 2024; 9 days ago (18 December 2024)
iOS, iPadOS131.0.6778.154[4] Edit this on Wikidata / 17 December 2024; 10 days ago (17 December 2024)
Extended Support Release130.0.6723.170[5] Edit this on Wikidata / 19 December 2024; 8 days ago (19 December 2024)
Preview release
Windows, macOS, Linux132.0.6834.46[6] Edit this on Wikidata / 11 December 2024; 16 days ago (11 December 2024)
Android132.0.6834.56[7] Edit this on Wikidata / 18 December 2024; 9 days ago (18 December 2024)
iOS, iPadOS132.0.6834.54[8] Edit this on Wikidata / 18 December 2024; 9 days ago (18 December 2024)
Written inC++, Assembly, Python, JavaScript
EngineWebKit (based on KHTML)
Operating systemLinux
Mac OS X (10.5 and later, Intel only)
Windows (XP SP2 and later)
Available in50 languages
TypeWeb browser
LicenseGoogle Chrome Terms of Service;[note 1]
WebKit: BSD/LGPL;
V8: BSD
Websitewww.google.com/chrome

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 2 September 2008, and the public stable release was on 11 December 2008. The name is derived from the graphical user interface frame, or "chrome", of web browsers. As of January 2011, Chrome was the third most widely used browser, and passed the 10% worldwide usage share of web browsers, according to Net Applications.[9]

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.[10][11] This move enabled third-party developers to study the underlying source code and to help convert 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.[12] The Google-authored portion of Chromium is released under the permissive BSD license,[13] which allows portions to be incorporated into both open source and closed source software programs.[14] Other portions of the source code are subject to a variety of open source licenses.[15] Chromium implements the same feature set as Chrome, but lacks built-in automatic updates and Google branding, and most noticeably has a blue-colored logo in place of the multicolored Google logo.[16]

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".[17]

Announcement

The release announcement was originally scheduled for 3 September 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.[18] Copies intended for Europe were shipped early and German blogger Philipp Lenssen of Google Blogoscoped[19] made a scanned copy of the 38-page comic available on his website after receiving it on 1 September 2008.[20] Google subsequently made the comic available on Google Books[21] and mentioned it on their official blog along with an explanation for the early release.[22]

Public release

An early version of Chromium for Linux, explaining the difference between Chrome and Chromium

The browser was first publicly released for Microsoft Windows (XP and later versions only) on 2 September 2008 in 43 languages, officially a beta version.[23] Chrome quickly gained about 1% market share despite being only available for Microsoft Windows.[22][24][25][26] 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.[27]

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.[28] The first official Chrome Mac OS X and Linux developer previews[29] were announced on 4 June 2009 with a blog post[30] 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.[31][32] Google Chrome 5.0, announced on 25 May 2010, was the first stable release to support all three platforms.[33]

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

Development

Usage share of alternative web browsers (non-IE) according to Stat Counter.

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.[35] 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.

Chrome uses the WebKit rendering engine to display web pages, on advice from the Android team.[21] 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.[21]

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

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.[37] – 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.[38]

On 11 January 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.[39]

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 programing 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.[40]

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.[41][42][43]

Release history

Color Meaning
Red Old release
Green Current stable release
Blue Current beta release
Purple Current dev release
Major version Release date WebKit version[44] V8 engine version[45] Operating system support Significant changes
0.2.149 2008-09-02 522 0.3 Windows First release.[46]
0.3.154 2008-10-29 Improved plugin performance and reliability. Spell checking for input fields. Improved web proxy performance and reliability. Tab and window management updates.
0.4.154 2008-11-24 525 Bookmark manager with import and export support. Privacy section added to the application options. New blocked popup notification. Security fixes.
1.0.154 2008-12-11 528 First stable release.
2.0.172 2009-05-24 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.[47]
3.0.195 2009-10-12 532 1.2 New "new tab" page for improved customization. 25% faster JavaScript. HTML5 video and audio tag support. Lightweight theming.
4.0.249 2010-01-25 532.5 1.3 Extensions, bookmark synchronization, enhanced developer tools, improved HTML5 support, performance improvements, full ACID3 pass, HTTP byte range support, increased security, and experimental new anti-reflected-XSS feature called "XSS Auditor".[48]
4.1.249 2010-03-17 Translate infobar, new privacy features, disabled XSS Auditor.[49]
5.0.375 2010-05-21 533 2.1 Windows
Mac
Linux 		Improved JavaScript performance, browser preference synchronizing, increased HTML5 support (Geolocation APIs, App Cache, web sockets, and file drag-and-drop), revamped bookmark manager, Adobe Flash Player integrated.[50][51]
6.0.472 2010-09-02 534.3 2.2 Updated and more streamlined UI, with simplified Omnibox, new tab page and merged menu buttons. Form Autofill. Expanded synchronization support to include extensions and Autofill data. Support for WebM videos. Improvements for performance and stability.[52] Built-in PDF support (disabled by default).[53]
7.0.517 2010-10-21 534.7 2.3.11.22 Primarily a stabilizing release with hundreds of bug fixes. Implemented HTML5 parsing algorithm, File API, directory upload via input tag. Mac OS X version gained AppleScript support for UI automation.[54] Late binding enabled for SSL sockets: High priority SSL requests are now always sent to the server first. New options for managing cookies. Updated New Tab Page to enable featuring of web applications.
8.0.552 2010-12-02 534.10 2.4.9.19 Chrome Web Store, built-in PDF viewer that works inside Chrome's sandbox for increased security, expanded synchronization support to include web applications, and improved plug-in handling.[55] 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é) for Mac OS.
9.0.597 2011-02-03 534.13 2.5.9.6 WebGL enabled by default, Adobe Flash sandboxing on Windows and Chrome Instant (à la Google Instant) option.[56] WebP support.[57] 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.
10.0.648 2011-03-08 534.16 3.0.12.30 Google Cloud Print sign-in interface enabled by default. Partially implemented sandboxing of the GPU process.[58][59][60] Faster JavaScript performance due to incorporation of Crankshaft, an improved compiler for V8.[61] 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.[62]
11.0.696 2011-04-15 534.24 3.1.8.3 HTML5 Speech Input API. [63] GPU-accelerated 3D CSS turned on by default. GPU-based hardware acceleration and WebGL disabled for Windows XP.[64] Updated icon.[65]
12.0.733 2011-04-12 534.29 3.2.9 Tab Multi-Select (Windows only): the ability to select multiple tabs, using the ctrl key, and applying actions (e.g. reload) to them all. New and improved bookmark bar animations. Confirm to Quit feature has been moved to the Chrome menu[66]

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[67] and stable. There are extensive differences from its peers in Chrome's minimalistic user interface,[21] which is atypical of modern web browsers.[68] For example, Chrome does not render RSS feeds.[69] 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.[70][71] 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.[72] 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.[73] Such a feature was already implemented in Konqueror in 2004.[citation needed]

Acid tests

The results of the Acid3 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.[74]

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.[21]

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.[75] 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";[76] 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.[21] 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.[77] On Linux sandboxing uses the seccomp mode.[78][79]

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.[21] Chrome supports the Netscape Plugin Application Programming Interface (NPAPI),[80] but does not support the embedding of ActiveX controls.[80] On 30 March 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.[81] Java applet support is available in Chrome with Java 6 update 12 and above.[82] Support for Java under Mac OS X was provided by a Java Update released on May 18, 2010.[83]

A private browsing feature called Incognito mode is provided that prevents the browser from storing any history information or cookies from the websites visited.[84] Chrome warns on the new tab page that "this feature does not make your actions on the internet invisible", however, and the browser advises the user to be wary of:

Incognito mode is similar to the private browsing feature introduced with Apple's Safari, Mozilla Firefox 3.5, Opera 10.5, and Internet Explorer 8.

Security vulnerabilities

See also: Comparison of web browsers § Vulnerabilities

On 12 January 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."[85]

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

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.[21] Tests by Google in September 2008 showed that V8 was about twice as fast as Firefox 3.0 and the WebKit nightlies.[citation needed]

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.[87] 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.[88][89][90][91][92][93] 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.[94]

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.[95][96][97] 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.[98]

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

Chrome uses DNS prefetching to speed up website lookups, as do Firefox[103] and Safari.[104] 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[105][106] 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.[107]

Stability

The Gears team implemented a multi-process architecture in Chrome,[108] similar to Loosely Coupled Internet Explorer (LCIE) implemented by Internet Explorer 8.[109] By default, a separate process is allocated to each site instance and plugin, a procedure referred to as process isolation.[110] 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,[111] 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.[112] Safari[113] and Firefox[114] 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.[21]

User interface

File:Google Chrome - Wikipedia, the free encyclopedia.png
Google Chrome's user interface on Mac OS X

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.[21]

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.[21] 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.[21] In Google Chrome 2.0, the New Tab Page was updated to allow users to hide thumbnails they did not want to appear.[115]

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.[116]

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.[117] However, this functionality is currently unavailable on the Linux and Mac platforms.[118]

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

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.[103]

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

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.[120][121]

File:Chrome Logo.svg
Logo used from the start of the Chrome project until March 2011

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."[122]

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).[21]

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.[123][124]

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.[125]

Criticism of the idea came quickly. Ryan Paul of Ars Technica said on 9 December 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."[125]

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

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,[127] 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 has prevented Google from including this as a default function.[128]

Extensions

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

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

As of 4 February 2011, the extension gallery featured over 11500 extensions,[132] including official extensions from The Independent,[133] CEOP,[134] Transport for London,[135] Cricinfo,[136] WOT: Web of Trust[137] and FIFA.[138]

Themes

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

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.[142]

Release channels and updates

On 8 January 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.[143][144] On 22 July 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.[145] 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.[146] It cannot be set as the default browser.

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,[147] or users can download a standalone version that does not autoupdate.[148][149] On Mac, it uses Google Update Service, and autoupdate can be controlled via the Mac OS X "defaults" system.[150] 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.[151]

Usage tracking

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

Tracking methods
Method[153] Information sent When Optional?
Installation Randomly generated token included in installer. Used to measure success rate of Google Chrome.[154]

On installation

No
RLZ identifier[155] Encoded string, according to Google, contains non-identifying information how Chrome was downloaded and its install week, and is used to measure promotional campaigns.[154] Google provides the source code to decode this string.[43]
  • On Google search query
  • On first launch and first use of address bar[154]
 Partial[note 2][154]
clientID[156] Unique identifier along with logs of usage metrics and crashes. Un­known Yes[157]
Suggest[156] Text typed into the address bar While typing Yes
Page not found Text typed into the address bar Upon receiving "Server not found" response Yes
Bug tracker Details about crashes and failures Un­known Yes[157]

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

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.[158]

System requirements

The recommended requirements for optimal performance of Chrome are:[159]

  • 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.[160][161]

Reception

Further information: Usage share of web browsers and Browser wars
Usage share of web browsers according to Stat Counter, Chrome was 17.4% in March 2011.[162]

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."[163]

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."[164] 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."[165] 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.[166][167]

Chrome's design bridges the gap between desktop and so-called "cloud computing." At the touch of a button, Chrome lets you make a desktop, Start menu, or Quick Launch shortcut to any Web page or Web application, blurring the line between what's online and what's inside your PC. For example, I created a desktop shortcut for Google Maps. When you create a shortcut for a Web application, Chrome strips away all of the toolbars and tabs from the window, leaving you with something that feels much more like a desktop application than like a Web application or page.

— PC World[168]

Criticism

User tracking

Concern about Chrome's optional usage collection and tracking have been noted in several publications.[169][170] On 2 September 2008, a CNET news item[171] 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.[172] 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.[173] Google noted that this change would "apply retroactively to all users who have downloaded Google Chrome."[174] 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.[175]

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.[176]

See also

Notes

  1. ^ An alternative and similar browser Chromium (except Chromium 5 beta) is open-sourced under BSD, MIT and some other free licenses; Google Chrome's WebKit layout engine and V8 JavaScript engine are all FOSS; the other parts may be FOSS or proprietary (see Chromium's Terms for a list). However, Google Chrome's Terms of Service makes the whole Google Chrome itself non-free and source closed (See Terms of Service text 9.2: You may not...).
  2. ^ Browser must be downloaded directly from the Google Chrome website to opt-out of the RLZ Identifier.

References

  1. ^ "Stable Channel Update for Desktop". 18 December 2024. Retrieved 19 December 2024.
  2. ^ "Stable Channel Desktop Update". 13 September 2023. Retrieved 14 September 2023.
  3. ^ "Chrome for Android Update". 18 December 2024. Retrieved 19 December 2024.
  4. ^ "Chrome Stable for iOS Update". 17 December 2024. Retrieved 17 December 2024.
  5. ^ "Extended Stable Updates for Desktop". 19 December 2024. Retrieved 19 December 2024.
  6. ^ "Chrome Beta for Desktop Update". 11 December 2024. Retrieved 11 December 2024.
  7. ^ "Chrome Beta for Android Update". 18 December 2024. Retrieved 18 December 2024.
  8. ^ "Chrome Beta for iOS Update". 18 December 2024. Retrieved 18 December 2024.
  9. ^ Net applications, retrieved January 2011.
  10. ^ Ryan Paul (2008-09-02). "Google unveils Chrome source code and Linux port". Ars Technica. Retrieved 2010-05-13.
  11. ^ "Google Chrome is built with open source code from Chromium." Retrieved from Chromium.org
  12. ^ "During a press briefing today, Google expressed hope that other browsers...", Retrieved from: Google unveils Chrome source code and Linux port, Ars Technica
  13. ^ "Home (Chromium Developer Documentation)". Chromium Developer Documentation. dev.chromium.org. 2009. Retrieved 2009-05-05.
  14. ^ "Google has made the Chrome source available under a permissive BSD license so that...", Retrieved from: Google unveils Chrome source code and Linux port, Ars Technica
  15. ^ "Chromium Terms and Conditions". Google Code. 2008-09-02. Retrieved 2008-09-03.
  16. ^ McAllister, Neil (2008-09-11). "Building Google Chrome: A first look". Fatal Exception. InfoWorld. Retrieved 2008-09-16. As the name suggests, Chromium is a rawer, less polished version of Chrome. The UI is mostly identical, with only a few very minor visual differences...The most readily evident difference is the logo, which sheds the Google colors in favor of a subdued blue design
  17. ^ Julia Angwin (2009-07-09). "Sun Valley: Schmidt Didn't Want to Build Chrome Initially, He Says". WSJ Digits Blog. Retrieved 2010-05-25.
  18. ^ Scott McCloud (2008-09-01). "Surprise!". Google Blogoscoped. Retrieved 2008-09-01.
  19. ^ Philipp Lenssen (2008-09-01). "Google Chrome, Google's Browser Project". Retrieved 2008-09-01.
  20. ^ Philipp Lenssen (2008-09-01). "Google on Google Chrome – comic book". Google Blogoscoped. Retrieved 2008-09-01.
  21. ^ a b c d e f g h i j k l m n o "Google Chrome". Google Book Search. 2008-09-01. Retrieved 2008-09-02.
  22. ^ a b Pichai, Sundar (2008-09-01). "A fresh take on the browser". Google Blog. Retrieved 2008-09-01. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  23. ^ "It was when not if... Google Chrome". 2008. Retrieved 2008-09-02. {{cite web}}: Unknown parameter |month= ignored (help)
  24. ^ "Google Chrome update: First screenshot, and live-blog alert". CNet. 2008-09-01. Retrieved 2008-09-02.
  25. ^ "Google launches Chrome web browser". The Canadian Press. Associated Press. 2008-09-02. Retrieved 2008-09-02.
  26. ^ "Come on Google... Chrome for Mac?". 2008. Retrieved 2008-11-22. {{cite web}}: Unknown parameter |month= ignored (help)
  27. ^ Gruener, Wolfgang (2009-01-03). "Google Chrome crosses 1% market share again". Chicago (IL): TG Daily. Retrieved 2009-01-03.
  28. ^ Shankland, Stephen (2009-01-09). "Chrome gets Mac deadline, extensions foundation". CNET. Retrieved 2009-01-13.
  29. ^ "Early Access Release Channels".
  30. ^ "Danger: Mac and Linux builds available". Retrieved 2009-06-09.
  31. ^ Mark Larson (2009-12-08). "Beta Update: Linux, Mac, and Windows". Google. Retrieved 2010-05-13.
  32. ^ a b "Google Chrome for the holidays: Mac, Linux and extensions in beta".
  33. ^ Brian Rakowski (2010-05-25). "A new Chrome stable release: Welcome, Mac and Linux!". Google. Retrieved 2010-05-25.
  34. ^ "Microsoft offers browser choices to Europeans". BBC News. 2010-03-01. Retrieved 2010-05-13.
  35. ^ Peteris Krumins (2008-09-05). "Code reuse in Google Chrome Browser". Retrieved 2010-05-13.
  36. ^ Ian Fette (2010-02-19). "Hello HTML5". Google. Retrieved 2010-05-24.
  37. ^ Paul, Ryan (2010). "Google offering MSI to simplify Chrome enterprise deployment". Ars Technica. Retrieved 16 December 2010. {{cite news}}: Unknown parameter |month= ignored (help)
  38. ^ "Google Update for Enterprise".
  39. ^ "HTML Video Codec Support in Chrome".
  40. ^ Kevin Purdy. "Chrome Canary Build Provides Bleeding-Edge Updates Alongside Stable Chrome". Lifehacker.com.
  41. ^ "Google Chrome, Chromium, and Google". blog.chromium.org/. The Chromium Blog. 2008. Retrieved 2010-02-17.
  42. ^ "Differences between Google Chrome and Linux distro Chromium". code.google.com/. Google Code. 2010. Retrieved 2010-09=01. {{cite web}}: Check date values in: |accessdate= (help)
  43. ^ a b c Google (2010). "In The Open, For RLZ". Retrieved 20 June 2010. {{cite web}}: |last= has generic name (help); Unknown parameter |month= ignored (help) Cite error: The named reference "ChromiumBlog20Jun10" was defined multiple times with different content (see the help page).
  44. ^ "Release Notes". The Chromium Projects.
  45. ^ "ChangeLog – v8".
  46. ^ "A Fresh take on the browser". 2008-09-01. Retrieved 2011-03-20.
  47. ^ "Google Chrome Releases: Stable Update: Google Chrome 2.0.172.28".
  48. ^ "Google Chrome Releases: Stable Channel Update".
  49. ^ Google Chrome Releases: Stable Channel Update 2010-03-17
  50. ^ Brian Rakowski (2010-05-25). "Evolving from beta to stable with a faster version of Chrome". Google. Retrieved 2010-05-25.
  51. ^ "Adobe Flash Player support now enabled in Google Chrome's stable channel". 2010-06-30. Retrieved 2010-08-08.
  52. ^ "Stable and Beta Channel Updates". Google Chrome Releases. 2010-09-02. Retrieved 2010-10-24.
  53. ^ "Bringing improved PDF support to Google Chrome". Chromium Blog. 2010-06-17. Retrieved 2010-10-24.
  54. ^ "Bringing another Chrome release to you, right on time". Google. Retrieved 2010-10-24.
  55. ^ "Stable, Beta Channel Updates". Google. Retrieved 2010-12-03.
  56. ^ "Safer plug-ins, faster search, and richer graphics". Google. Retrieved 2010-12-17.
  57. ^ "WebP Home". Google. Retrieved 2011-02-03.
  58. ^ "Dev Channel Update". Google. Retrieved 2011-01-21.
  59. ^ "Dev Channel Update". Google. Retrieved 2011-01-21.
  60. ^ "Issue 48607: Sandbox GPU process".
  61. ^ "A New Crankshaft for V8". Google. Retrieved 2010-12-17.
  62. ^ "A New Crankshaft for V8". Google. Retrieved 2010-12-17.
  63. ^ "Chrome Beta Release". 2011-03-22. Retrieved 2011-03-23.
  64. ^ "Dev Channel Update".
  65. ^ "Google Chrome Blog: A fresh take on an icon".
  66. ^ "Dev Channel Update".
  67. ^ "Technology overview – Google chrome".
  68. ^ Gloson (2008-12-04). "Google Chrome's Unique Features". Retrieved 2010-05-13.
  69. ^ [1], chromium issue tracker.
  70. ^ Stephen Shankland (2008-09-02). "Speed test: Google Chrome beats Firefox, IE, Safari – Business Tech". CNET News. Retrieved 2010-05-13.
  71. ^ Kevin Purdy (2009-06-11). "Lifehacker Speed Tests: Safari 4, Chrome 2, and More – Browsers". Lifehacker. Retrieved 2010-05-13.
  72. ^ 12 Unique features of Google Chrome, TechStroke
  73. ^ Rafe Needleman (2008-05-14). "The future of the Firefox address bar". CNET News. Retrieved 2010-05-13.
  74. ^ Anthony Laforge (2010-01-25). Stable Channel Update "Stable Channel Update". Google. Retrieved 2010-05-25. {{cite web}}: Check |url= value (help)
  75. ^ Chung, Marc (2008-09-05). "chromes-process model explained". Retrieved 2008-09-10.
  76. ^ Google (2008-09-01). "Google Chrome". Retrieved 2008-09-03. {{cite web}}: |author= has generic name (help)[dead link‍]
  77. ^ Barth, Adam. "The Security Architecture of the Chromium Browser" (PDF). Stanford Security Laboratory. Retrieved 2008-09-11. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  78. ^ Markus Gutschke (2009-05-06). "Re: [[PATCH 2/2]] x86-64: seccomp: fix 32/64 syscall hole". Retrieved 17 February 2011. {{cite web}}: URL–wikilink conflict (help)
  79. ^ Jake Edge (August 19, 2009). "Google's Chromium sandbox". Retrieved 17 February 2011.
  80. ^ a b "Google Chrome FAQ for web developers".
  81. ^ Paul, Ryan (2010). "Google bakes Flash into Chrome, hopes to improve plug-in API". Retrieved 2010-03-14. {{cite web}}: Unknown parameter |month= ignored (help)
  82. ^ "Java and Google Chrome". Java.com. Retrieved 2009-12-11.
  83. ^ "Issue 10812 – chromium – No java plugin support yet". google.com. Retrieved 2010-05-18.
  84. ^ "Explore Google Chrome Features: Incognito Mode". 2008-09-02. Retrieved 2008-09-04.
  85. ^ US-CERT (2011). "Vulnerability Note VU#258423 - Google Chrome multiple vulnerabilities". Retrieved 19 January 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  86. ^ Gregg Keizer, Google's Chrome untouched at Pwn2Own hack match, Computerworld, March 10, 2011
  87. ^ "V8 Benchmark suite". Google code. Retrieved 2008-09-03.
  88. ^ Rupert Goodwins (2008-09-02). "Google Chrome – first benchmarks. Summary: wow". Retrieved 2008-09-03.
  89. ^ "Google Chrome Javascript Benchmarks". 2008-09-02. Retrieved 2008-09-03. [dead link‍]
  90. ^ Adrian Kingsley-Hughes (2008-09-02). "Google Chrome is insanely fast ... faster than Firefox 3.0". Retrieved 2008-09-03.
  91. ^ Stephen Shankland (2008-09-02). "Speed test: Google Chrome". CNET Business Tech. Retrieved 2008-09-03.
  92. ^ Alexander Limi (2008-09-02). "Chrome: Benchmarks and more". Retrieved 2010-05-13.
  93. ^ Vygantas Lipskas (2009-03-01). "Safari 4 vs. Firefox 3 vs. Google Chrome vs. Opera 10, 9.6 vs. Internet Explorer 8, 7". Favbrowser. Retrieved 2010-05-13.
  94. ^ Scott M. Fulton, III (2010-10-11). "Firefox in the dust: Opera poised to reclaim browser performance lead". Retrieved 2010-11-06.
  95. ^ Stephen Shankland (2008-09-03). "Firefox counters Google's browser speed test – Business Tech". CNET News. Retrieved 2010-05-13.
  96. ^ Eich, Brendan (2008-09-03). "TraceMonkey Update". Retrieved 2008-09-03.
  97. ^ Stephen Shankland (2008-11-03). "Third Chrome beta another notch faster – News". Builder AU. Retrieved 2010-05-13.
  98. ^ Resig, John (2008-09-03). "JavaScript Performance Rundown". Retrieved 2008-06-09.
  99. ^ Maciej Stachowiak (2008-09-18). "WebKit blog: Introducing SquirrelFish Extreme". Retrieved 2010-05-13.
  100. ^ Cameron Zwarich (2008-09-18). "SquirrelFish Extreme has landed!". Retrieved 2010-05-13.
  101. ^ Stephen Shankland (2008-09-22). "Step aside, Chrome, for Squirrelfish Extreme – News". Builder AU. Retrieved 2010-05-13.
  102. ^ Charles Ying (2008-09-19). "SquirrelFish Extreme: Fastest JavaScript Engine Yet". Retrieved 2010-05-13.
  103. ^ a b Preston Gralla (2008-09-03). "Three hidden Chrome features you'll love". Retrieved 2008-09-16.
  104. ^ Apple Inc. (2010-06-07). "What's new in Safari 5". Retrieved 2010-07-06.
  105. ^ "Chromium SPDY client implementation".
  106. ^ "Chromium: SPDY proxy examples".
  107. ^ "spdy-dev mailing list: SPDY on Google servers?".
  108. ^ Charlie Reisn (2008-09-11). "Multi-process Architecture". Retrieved 2008-09-12.
  109. ^ Andy Zeigler (2008-03-11). "IE8 and Loosely-Coupled IE (LCIE)". Retrieved 2008-09-12.
  110. ^ Chromium Developer Documentation (2008-09-03). "Process Models". Retrieved 2008-09-12.
  111. ^ Brian Prince (2008-12-11). "Google Chrome Puts Security in a Sandbox". Retrieved 2010-06-04.
  112. ^ Google (2008-09-21). "Google Chrome book". Retrieved 2008-09-21. {{cite web}}: |author= has generic name (help)
  113. ^ "Webkit.org".
  114. ^ "Firefox Lorentz beta available for download and testing". Mozilla. 2010-04-08.
  115. ^ "A Speedier Google Chrome for all users – Google Chrome Blog".
  116. ^ Anthony Laforge (2009-09-15). "Google Chrome after a year: Sporting a new stable release". Google. Retrieved 2010-05-13.
  117. ^ Kevin Purdy (2009-09-02). "Add a Bookmark Button to Google Chrome's Toolbar". Lifehacker. Retrieved 2010-05-13.
  118. ^ Google (2009). "Issue 21152: Expose UI for bookmark menu on all platforms". Retrieved 2009-12-30. {{cite web}}: |last= has generic name (help); Unknown parameter |month= ignored (help)
  119. ^ "Google Chrome with 3D". Google. 2009-04-01. Retrieved 2009-05-26.
  120. ^ "Chromium url_constants.cc". Retrieved 2010-09-01.
  121. ^ Pash, Adam (2010). "Chrome's About:Labs Renamed to About:Flags, Adds a Warning". LifeHacker. Retrieved 19 October 2010. {{cite news}}: Unknown parameter |month= ignored (help)
  122. ^ Rura, Steve (2011). "A fresh take on an icon". Retrieved 22 March 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  123. ^ "Chrome Web Store". Google. 2010-05-19. Retrieved 2010-05-24.
  124. ^ Erik Lay (2010-05-19). "The Chrome Web Store". Google. Retrieved 2010-05-24.
  125. ^ a b Paul, Ryan (2010). "Chrome Web Store: a solution in search of a problem?". Ars Technica. Retrieved 10 December 2010. {{cite news}}: Unknown parameter |month= ignored (help)
  126. ^ Google (2011). "A dash of speed, 3D and apps". Retrieved 7 February 2011. {{cite web}}: |last= has generic name (help); Unknown parameter |month= ignored (help)
  127. ^ "Issue 8036: Show thumbnails for open tabs on Windows 7 superbar (Aero Peek)".
  128. ^ "Issue 37957: Investigate solutions for Aero Peek flooding users with tab thumbnails".
  129. ^ Aaron Boodman (2009-09-09). "Extensions Status: On the Runway, Getting Ready for Take-Off". Google. Retrieved 2010-05-13.
  130. ^ Erik Kay (2009-12-08). "Extensions beta launched, with over 300 extensions!". Google. Retrieved 2010-05-13.
  131. ^ Nick Baum (2010-01-25). "Over 1,500 new features for Google Chrome". Google Chrome Blog. Retrieved 2010-05-13.
  132. ^ "Security improvements and registration updates for the Google Chrome Extensions Gallery". 2010-08-19.
  133. ^ "Official Independent Chrome Extension".
  134. ^ "CEOP Official Chrome Extension".
  135. ^ "Official TfL Chrome Extension".
  136. ^ "ESPN Cricinfo".
  137. ^ "WOT – Google Chrome extension gallery".
  138. ^ "Official World Cup FIFA Chrome Extension".
  139. ^ Glen Murphy (2009-10-05). "A splash of color to your browser: Artist Themes for Google Chrome". Google Chrome Blog. Retrieved 2010-05-13.
  140. ^ "Google Chrome Themes Gallery".
  141. ^ Basic settings: Change browser theme Google Chrome Help
  142. ^ "Support Google Chrome – Automatic web page translation".
  143. ^ Mark Larson (2009-01-08). "Google Chrome Release Channels". Retrieved 2009-01-09.
  144. ^ Mark Larson (2009-01-08). "Dev update: New WebKit version, new features, and a new Dev channel". Retrieved 2009-01-09.
  145. ^ Anthony Laforge (2010-07-22). "Release Early, Release Often". Retrieved 2010-07-25.
  146. ^ Lee Mathews (2010-07-23). "Google drops Chrome Canary build down the Chrome mineshaft". Retrieved 2010-07-25.
  147. ^ David Dorwin (2009-05-14). "Google Update Releases Update Controls". Retrieved 2010-05-13.
  148. ^ "standalone download page".
  149. ^ Alex Chitu (2009-03-01). "Standalone Offline Installer for Google Chrome". Google Operating System. Retrieved 2010-05-13.
  150. ^ "Google Help page "Managing updates in Google Software Update"".
  151. ^ Stephen Adams (2009-07-15). "Chromium Blog: Smaller is Faster (and Safer Too)". Retrieved 2010-05-13.
  152. ^ "Communications between Chromium/Google Chrome and service providers".
  153. ^ a b "SRWare Iron webpage". Retrieved 2008-10-12.
  154. ^ a b c d "Google Chrome Privacy Whitepaper" (PDF).
  155. ^ "&rlz= in Google referrer: Organic traffic or AdWords?". Retrieved 2009-02-27.
  156. ^ a b c "Google Reacts to Some Chrome Privacy Concerns". Retrieved 2008-09-24.
  157. ^ a b Controlled by the setting "Send usage statistics and error reports". Default off.
  158. ^ "Google Chrome Unique Identifier Change". 2010-03-16. Retrieved 2010-03-24.
  159. ^ Google. "System requirements : Install or update Google Chrome : Google Chrome Help". Retrieved 2011-04-08. {{cite web}}: |author= has generic name (help)
  160. ^ Google. "64-bit Support — The Chromium Projects". Retrieved 2011-04-08. {{cite web}}: |author= has generic name (help)
  161. ^ Google. "Google Chrome for Linux - Terms and Conditions Agreement". Retrieved 2011-04-08. {{cite web}}: |author= has generic name (help)
  162. ^ Stat Counter, March 2011, retrieved 2 April 2011
  163. ^ Moore, Matthew (2008-09-02). "Google Chrome browser: Review of reviews". Daily Telegraph. Telegraph Media Group. Retrieved 2008-09-04.
  164. ^ Liedtke, Michael (2008-09-03). "Google polishes product line with Chrome browser" (Document). Associated Press. {{cite document}}: Unknown parameter |url= ignored (help)
  165. ^ Jaroslovsky, Rich (2010-02-25). "Browser Wars: The Sequel" (Document). BusinessWeek. {{cite document}}: Unknown parameter |url= ignored (help)
  166. ^ "Thoughts on Chrome & More". John's Blog. 2008-09-01. Retrieved 2010-05-13.
  167. ^ Collins, Barry (2008-09-02). "Mozilla: Google's not trying to kill us" (Document). PC Pro. {{cite document}}: Unknown parameter |url= ignored (help)
  168. ^ Mediati, Nick (2008-09-03). "Google Chrome Web Browser". PC World. Retrieved 2008-09-07.
  169. ^ Ackerman, Elise. "Google browser's tracking feature alarms developers, privacy advocates". Mercury News.
  170. ^ "Google's Omnibox could be Pandora's box". 2008-09-03. Retrieved 2008-09-04.
  171. ^ "Be sure to read Chrome's fine print". CNET. Retrieved 2008-09-03.
  172. ^ "Google Terms of Service".
  173. ^ "Google Chrome Terms of Service (English)". Retrieved 2008-09-04.
  174. ^ "Google Amends Chrome License Agreement After Objections" (Document). PC World. 2008-09-03. {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)
  175. ^ "Google Chrome Privacy Notice". Retrieved 2009-10-27.
  176. ^ Fried, Ina (2008-09-03). "Google's Omnibox could be Pandora's box". Retrieved 2010-05-13.
Wikinews has related news:
Wikimedia Commons has media related to Google Chrome.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Google_Chrome&oldid=424673638"