Jump to content

Google Chrome: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Moroz1975 (talk | contribs)
99 edits
Line 503: Line 503:
Two weeks after Chrome's launch, the WebKit team announced a new JavaScript engine, [[WebKit#Further development|SquirrelFish Extreme]],<ref>{{cite web|url= http://webkit.org/blog/214/introducing-squirrelfish-extreme/ |title= WebKit blog: Introducing SquirrelFish Extreme |author=Maciej Stachowiak |date= September 18, 2008 |accessdate=May 13, 2010}}</ref> citing a 36% speed improvement over Chrome's V8 engine.<ref>{{cite web|url= http://summerofjsc.blogspot.com/2008/09/squirrelfish-extreme-has-landed.html |title= SquirrelFish Extreme has landed! |author=Cameron Zwarich |date= September 18, 2008 |accessdate=May 13, 2010}}</ref><ref>{{cite web|url= http://www.builderau.com.au/news/soa/Step-aside-Chrome-for-Squirrelfish-Extreme/0,339028227,339292128,00.htm?feed=pt_performance |title= Step aside, Chrome, for Squirrelfish Extreme – News |author=Stephen Shankland |publisher=Builder AU |date= September 22, 2008 |accessdate=May 13, 2010}}</ref><ref>{{cite web|url= http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/ |title= SquirrelFish Extreme: Fastest JavaScript Engine Yet |author=Charles Ying |date= September 19, 2008 |accessdate=May 13, 2010}}</ref>
Two weeks after Chrome's launch, the WebKit team announced a new JavaScript engine, [[WebKit#Further development|SquirrelFish Extreme]],<ref>{{cite web|url= http://webkit.org/blog/214/introducing-squirrelfish-extreme/ |title= WebKit blog: Introducing SquirrelFish Extreme |author=Maciej Stachowiak |date= September 18, 2008 |accessdate=May 13, 2010}}</ref> citing a 36% speed improvement over Chrome's V8 engine.<ref>{{cite web|url= http://summerofjsc.blogspot.com/2008/09/squirrelfish-extreme-has-landed.html |title= SquirrelFish Extreme has landed! |author=Cameron Zwarich |date= September 18, 2008 |accessdate=May 13, 2010}}</ref><ref>{{cite web|url= http://www.builderau.com.au/news/soa/Step-aside-Chrome-for-Squirrelfish-Extreme/0,339028227,339292128,00.htm?feed=pt_performance |title= Step aside, Chrome, for Squirrelfish Extreme – News |author=Stephen Shankland |publisher=Builder AU |date= September 22, 2008 |accessdate=May 13, 2010}}</ref><ref>{{cite web|url= http://www.satine.org/archives/2008/09/19/squirrelfish-extreme-fastest-javascript-engine-yet/ |title= SquirrelFish Extreme: Fastest JavaScript Engine Yet |author=Charles Ying |date= September 19, 2008 |accessdate=May 13, 2010}}</ref>


Chrome uses [[Domain Name System|DNS]] prefetching to speed up website lookups, <ref name="features">{{cite web |url=http://blogs.computerworld.com/three_hidden_chrome_features_youll_love |title=Three hidden Chrome features you'll love |author=Preston Gralla |date=September 3, 2008 |accessdate=September 16, 2008}}</ref> as do Firefox{{citation needed|date=February 2012}} and Safari.<ref>{{cite web |url=http://www.apple.com/safari/whats-new.html#performance |title=What's new in Safari 5 |author=Apple Inc. |date=June 7, 2010 |accessdate=July 6, 2010}}</ref> This feature is available in Internet Explorer 9 called DNS Pre-resolution<ref>[http://blogs.msdn.com/b/ie/archive/2011/03/17/internet-explorer-9-network-performance-improvements.aspx Internet Explorer 9 Network Performance Improvements]</ref>, and in [[Opera (web browser)|Opera]] as a UserScript<ref>[http://userjs.org/scripts/browser/enhancements/page-prefetcher Page prefetcher]</ref>.
Chrome uses [[Domain Name System|DNS]] prefetching to speed up website lookups, <ref name="features">{{cite web |url=http://blogs.computerworld.com/three_hidden_chrome_features_youll_love |title=Three hidden Chrome features you'll love |author=Preston Gralla |date=September 3, 2008 |accessdate=September 16, 2008}}</ref> as do Firefox from version Firefox 3.1 beta2<ref>{{cite web |url=http://bitsup.blogspot.com/2008/11/dns-prefetching-for-firefox.html |title=DNS prefetching for Firefox |date=November 8, 2008}}</ref> and Safari since version 5.<ref>{{cite web |url=http://www.apple.com/safari/whats-new.html#performance |title=What's new in Safari 5 |author=Apple Inc. |date=June 7, 2010 |accessdate=July 6, 2010}}</ref> This feature is also available in Internet Explorer 9 called DNS Pre-resolution<ref>[http://blogs.msdn.com/b/ie/archive/2011/03/17/internet-explorer-9-network-performance-improvements.aspx Internet Explorer 9 Network Performance Improvements]</ref>, and in [[Opera (web browser)|Opera]] as a UserScript (not built-in)<ref>[http://userjs.org/scripts/browser/enhancements/page-prefetcher Page prefetcher]</ref>.


Chrome utilizes the faster [[SPDY]] protocol instead of [[HTTP]]<ref>{{cite web|url=http://src.chromium.org/viewvc/chrome/trunk/src/net/spdy/|title=Chromium SPDY client implementation}}</ref><ref>{{cite web|url=http://www.chromium.org/spdy/spdy-proxy-examples|title=Chromium: SPDY proxy examples}}</ref> 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 [[Secure Sockets Layer|SSL]]-enabled servers.<ref>{{cite web|url=http://groups.google.com/group/spdy-dev/browse_thread/thread/4c2396ecbc36b1c4|title=spdy-dev mailing list: SPDY on Google servers?}}</ref>
Chrome utilizes the faster [[SPDY]] protocol instead of [[HTTP]]<ref>{{cite web|url=http://src.chromium.org/viewvc/chrome/trunk/src/net/spdy/|title=Chromium SPDY client implementation}}</ref><ref>{{cite web|url=http://www.chromium.org/spdy/spdy-proxy-examples|title=Chromium: SPDY proxy examples}}</ref> 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 [[Secure Sockets Layer|SSL]]-enabled servers.<ref>{{cite web|url=http://groups.google.com/group/spdy-dev/browse_thread/thread/4c2396ecbc36b1c4|title=spdy-dev mailing list: SPDY on Google servers?}}</ref>

Revision as of 16:28, 12 March 2012

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.69/70[1] Edit this on Wikidata / 12 November 2024; 6 days ago (12 November 2024)
Windows Server 2012/2012 R2109.0.5414.165[2] / 13 September 2023; 14 months ago (2023-09-13)
Android131.0.6778.39 Edit this on Wikidata / 12 November 2024; 6 days ago (12 November 2024)
iOS, iPadOS131.0.6778.73[3] Edit this on Wikidata / 12 November 2024; 6 days ago (12 November 2024)
Extended Support Release130.0.6723.127[4] Edit this on Wikidata / 12 November 2024; 6 days ago (12 November 2024)
Preview release
Windows, macOS, Linux132.0.6834.6[5] Edit this on Wikidata / 13 November 2024; 5 days ago (13 November 2024)
Android131.0.6778.39[6] Edit this on Wikidata / 6 November 2024; 12 days ago (6 November 2024)
iOS, iPadOS132.0.6834.4[7] Edit this on Wikidata / 13 November 2024; 5 days ago (13 November 2024)
Written inC++, Assembly, Python, JavaScript
EngineWebKit (based on KHTML)
Operating systemLinux
Mac OS X (10.5 and later, Intel only)
Microsoft Windows (XP SP2 and later)
Android (4.0 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 freeware 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.[citation needed] As of January 2012, Google Chrome has approximately 25-28% worldwide usage share of web browsers, making it the second or the third most widely used browser, according to different estimates.[8][9][10][11] According to StatCounter,[9] Chrome overtook Firefox in November 2011, and is the most popular browser in India[12], Pakistan,[13] Russia,[14] and South America.[15]

In September 2008, Google released a large portion of Chrome's source code, including its V8 JavaScript engine, as an open source project called Chromium.[16][17] 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 the V8 JavaScript engine to improve web application performance.[18] The Google-authored portion of Chromium is released under the permissive BSD license,[19] which allows portions to be incorporated into both open source and closed source software programs.[20] Other portions of the source code are subject to a variety of open source licenses.[21] Chromium implements a similar feature set as Chrome, but lacks built-in automatic updates, built-in PDF reader and Google branding, and has a blue-colored logo instead of the multicolored Google logo.[22][23]

On February 7, 2012, Google launched Google Chrome Beta for Android 4.0 (Ice Cream Sandwich) devices.[24]

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, Schmidt admitted that "It was so good that it essentially forced me to change my mind".[25]

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 within the new browser.[26] Copies intended for Europe were shipped early and German blogger Philipp Lenssen of Google Blogoscoped[27] made a scanned copy of the 38-page comic available on his website after receiving it on September 1, 2008.[28] Google subsequently made the comic available on Google Books[29] and mentioned it on their official blog along with an explanation for the early release.[30]

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) on September 2, 2008 in 43 languages, officially a beta version.[31] Chrome quickly gained about 1% market share.[30][32][33][34] 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.[35]

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.[36] The first official Chrome Mac OS X and Linux developer previews[37] were announced on June 4, 2009 with a blog post[38] 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.[39][40] Google Chrome 5.0, announced on May 25, 2010, was the first stable release to support all three platforms.[41]

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

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

Usage share of web browsers (excluding IE) according to StatCounter[44]

Chrome uses the WebKit rendering engine to display web pages, on advice from the Android team.[29] Chrome is tested internally with unit testing, "automated user interface testing of scripted user actions", fuzz testing, as well as WebKit's layout tests (99% of which Chrome is claimed to have passed) and against commonly accessed websites inside the Google index within 20–30 minutes.[29]

Google created Gears for Chrome, which added features for web developers typically relating to the building of web applications, including offline support.[29] However, Google phased out Gears in favor of HTML5.[45]

On January 11, 2011 the Chrome Product manager, Mike Jazayeri, announced that Chrome will no longer support H.264 video codec for its HTML5 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.[46] As of January 2012, there has been no announcement yet of which future version of Chrome will actually implement the removal of H.264 support.

Enterprise deployment

In December 2010 Google announced that to make deploying Chrome easier in a business environment they would provide an official Chrome MSI package. For Enterprise deployments it's important to have full-fledged MSI packages that can be customized via transform files, but the provided MSI is only a very limiting MSI wrapper around the normal installer that does not fulfill all Enterprise needs.[47] The normal downloaded Chrome installer puts the browser in the user's local app data 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[48] – 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, disable auto updates, a home page and to workaround their basic Windows design flaws and bugs if it comes to roaming profiles support, etc.[49] Until version 18 the software is known not to be ready for Enterprise deployments with roaming profiles.[50]

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

Chromium

Main article: Chromium (web browser)

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 license than the compiled builds of Chrome, and does not implement user RLZ tracking.[52][53][54]

2011

Due to a faulty virus definition update on September 30, 2011, Microsoft Security Essentials incorrectly identified Google Chrome as malware and began deleting it from user's systems.[55][56][57][58]

2012

In an advertising campaign not authorized by Google, marketing companies hired by Google offered to pay individuals to link to a video promoting Google Chrome for businesses. The campaign violated Google's ad guidelines on paid links. In response, Google demoted google.com/chrome in its search results for 60 days starting January 3.[59]

On February 7, Google Chrome Beta was launched for Android 4.0[60] for selected countries.[61]

Release history

Legend:

Color Meaning
Red Old release
Green Current stable release
Blue Current beta release
Purple Current dev release

Note: All versions support Windows. Mac and Linux are supported starting with version 5.0.375. The Android 4.0 platform is first supported in 0.16.4130.199 (Chrome for Android).[62][63][64]

Major version Release date WebKit version[65] V8 engine version[66] Significant changes
0.2.149 2008-09-02 522 0.3
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.[68]
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.
  • Experimental new anti-reflected-XSS feature called "XSS Auditor".[69]
4.1.249 2010-03-17
  • Translate infobar.
  • New privacy features.
  • Disabled XSS Auditor.[70]
5.0.375 2010-05-21 533 2.1
6.0.472 2010-09-02 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.
  • Built-in PDF support (disabled by default).[73]
7.0.517 2010-10-21 534.7 2.3.11.22
  • Implemented HTML5 parsing algorithm.
  • File API.
  • Directory upload via input tag.
  • Mac OS X version gained AppleScript support for UI automation.[74]
  • 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.
  • Improved plug-in handling.[75]
  • 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.[76]
  • WebP support.[77]
  • 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.[78][79][80]
  • Faster JavaScript performance due to incorporation of Crankshaft, an improved compiler for V8.[81]
  • 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.[82]
11.0.696 2011-04-27 534.24 3.1.8.16
  • HTML5 Speech Input API.[83]
  • Updated icon.[84]
12.0.742 2011-06-07 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.[85]
  • 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.[85]
  • 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.[86]
13.0.782 2011-08-02 535.1 3.3.10.30
  • Instant Pages (pre-rendering of webpages).[87]
  • Native print interface and preview (Linux and Windows only).
  • New chrome://flags experiments: Experimental new tab page, Restrict Instant To Search.
14.0.835 2011-09-16 3.4.14.21
  • Native Client (NaCl) enabled for apps in the Chrome Web Store.[88]
  • 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.[89] DNSSEC
  • Validation of HTTPS sites.[90]
15.0.874 2011-10-25 535.2 3.5.10.24
  • Faster print preview.[91]
  • Redesigned new tab page on by default.[91]
  • JavaScript fullscreen API enabled by default.[91]
  • Inline installation of Chrome Web Store items by verified sites.
  • Omnibox History synchronization.[92]
  • Switched to FFmpeg native VP8 decoder.[93]
  • Extensions integrated into settings pages.
  • GPU Accelerated Canvas 2D disabled.
16.0.912 2011-12-13 535.7 3.6.6.19
  • Multiple profiles on by default.[92]
  • Optional permissions in Chrome extensions, so the user can opt-in or opt-out of the optional permissions at installation time.[94]
  • Experimental support for side tabs was removed.[95]
17.0.963 2012-02-08 535.11 3.7.12.29
  • Updated Omnibox prerendering of pages.[96]
  • Download scanning protection.[96]
  • New extensions APIs.[96]
  • Improved History tab.
  • Removal of "+" symbol from the "new tab" button.
  • Added limited support for changing User Agent Strings.
  • Adjustable margins in Print Preview.[97]
18.0.1025 2012-01-24 535.19 3.8.9.5
  • Enabled GPU-accelerated rendering 2D Canvas.
  • When a profile is synced, use Google OAuth userinfo API to get profile information.[citation needed]
  • Added support for manifest_version attribute for extensions.
  • Folders in the wrench menu and application menu are greyed out.
  • Better error handling in audio wave out.
  • Made URL filter for web request API mandatory.
  • Rejects weak RSA and DSA keys when validating certificate chains for HTTPS.
  • Pop-ups opened from a maximized window now unmaximized.
  • Hide panels in presence of full screen app for windows.
  • Provide windows notification of thread termination.
  • Abort in-flight load tasks if the DB has been closed.[citation needed]
19.0.1061 2012-02-14 536.3 3.9.13
  • V8 engine supports « JavaScript Harmony » (ECMAScript 6).
  • Open incognito windows created extra normal windows when the session was restored.
  • Use Google’s online spellchecker to identify misspelled words as well as provide suggestions, for pasted text only.
  • When translating a page, get the code and translation via HTTPS.
  • Redesigned Settings and History UI[98]

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[99] and stable. There are extensive differences from its peers in Chrome's minimalistic user interface,[29] which is atypical of modern web browsers.[100] For example, Chrome does not render RSS feeds.[101] 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.[102][103] 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.[104] 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.[105]

Web standards support

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

On Ecma International's ECMAScript standards conformance Test 262[107] (version ES5.1 of 2012-02-29), Chrome version 17.0.963.79 scored 218/11563. The beta version 18.0.1025.54 scored 43/11563. The dev version 19.0.1061.1 scored 23/11563. 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.[108]

On the HTML5 test (1 January 2012 version), Chrome version 17.0.963.79 scored 374 out of 475, with 13 bonus points. The beta version 18.0.1025.54 scored 377 out of 475, with 13 bonus points. The dev version 19.0.1061.1 scored 379 out of 475, with 13 bonus points.[109]

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

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.[110] 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";[111] 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.[29] 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.[112] On Linux sandboxing uses the seccomp mode.[113][114]

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

Security vulnerabilities

See also: Comparison of web browsers § Vulnerabilities

No security vulnerabilities in Chrome had been successfully exploited in the three years of Pwn2Own from 2009-11.[119] However Chrome was the first browser to to be defeated at Pwn2Own 2012, by a French team who used zero day exploits to take complete control of a fully patched 64-bit Windows 7 PC using a booby-trapped website that overcame Chrome's sandboxing. It was also compromised twice at the 2012 CanSecWest Pwnium.[120][121][122]

Google's official response to the vulnerabilities was delivered by Jason Kersey, who said: "Congratulations to PinkiePie (aka PwniePie) for a beautiful piece of work to close out the Pwnium competition! We’re delighted at the success of Pwnium and the ability to study full exploits. We anticipate landing additional changes and hardening measures for both CVE-2011-3046 and CVE-2011-3047 in the near future. We also believe that both submissions are works of art and deserve wider sharing and recognition. We plan to do technical reports on both Pwnium submissions in the future."[123]

Malware blocking

A study has shown that users are four times more likely to be tricked into downloading malware than be compromised by an exploit.[124] Chrome 17 introduced download scanning protection.[96] An older study reported Chrome 10 blocked only 13% of malicious URLs, the same as Safari and Firefox, behind Internet Explorer 9 which blocked 92%, and 100% with application-based filtering enabled. Exploits that install malware without the user being aware (for example clickjacking and drive-by downloads) were not included in this particular study.[125][126]

Privacy

Privacy mode

The private browsing feature called Incognito mode prevents the browser from storing any history information or cookies from the websites visited. [127] 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.

Usage tracking

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

Tracking methods
Method[129] Information sent When Optional?
Installation Randomly generated token included in installer. Used to measure success rate of Google Chrome once at installation.[130]

On installation

No
RLZ identifier[131] Encoded string, according to Google, contains non-identifying information how Chrome was downloaded and its install week, and is used to measure promotional campaigns.[130] Google provides the source code to decode this string.[54]
  • On Google search query
  • On first launch and first use of address bar[130]
 Partial[note 2][130]
clientID[132] Unique identifier along with logs of usage metrics and crashes. Un­known Yes[133]
Suggest[132] 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[133]
Google Updater Details about Chrome version Un­known Yes
Downloads Chrome sends the URL and IP of the host and other meta data, such as the file’s hash and binary size, to Google. When downloading files Yes

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

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

Concern about Chrome's optional usage collection and tracking have been noted in several publications.[136][137] On September 2, 2008, a CNET news item[138] 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.[139] 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.[140] Google noted that this change would "apply retroactively to all users who have downloaded Google Chrome".[141] 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.[142]

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/bonnet-privacy box.[143]

Do Not Track

Main article: Do not track header

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 through web advertising, will provide much more detailed information on user behavior and that do not track would hurt Google's ability to exploit this. Software reviewer Kurt Bakke of Conceivably Tech wrote: "Google said that it intends charge [sic] 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."[144][145][146]

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 remains unclear as to 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.[147]

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

In February 2012, Google announced that Chrome will incorporate a Do Not Track feature, by the end of 2012.[149]

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.[29] 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.[150] 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.[151][152][153][154][155][156] 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.[157]

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

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

Chrome uses DNS prefetching to speed up website lookups, [166] as do Firefox from version Firefox 3.1 beta2[167] and Safari since version 5.[168] This feature is also available in Internet Explorer 9 called DNS Pre-resolution[169], and in Opera as a UserScript (not built-in)[170].

Chrome utilizes the faster SPDY protocol instead of HTTP[171][172] 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.[173]

Stability

A multi-process architecture is implemented in Chrome[174] where, by default, a separate process is allocated to each site instance and plugin. This procedure is termed process isolation,[175] and it prevents tasks from interfering with each other, raising security and stability. An attacker successfully gaining access to one application gains access to no others,[176] and failure in one instance results in a Sad Tab screen of death, similar to the well-known Sad Mac, but only one 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 needs further memory allocations.[177] This architecture is being adopted in upcoming versions of Safari[178] and Firefox.[179] Thus, in the near future most common browsers will use a multi-process architecture.

Chrome includes a process management utility called Task Manager which lets users see what sites and plugins are using the most memory, downloading the most bytes and overusing the CPU and provides the ability to terminate them.[29]

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 main 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, with their state, can be transferred seamlessly between window containers by dragging. Each tab has its own set of controls, including the Omnibox.[29]

The Omnibox is a URL box that combines the functions 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 Instant), and popular searches. Although Instant can be turned off, suggestions based on previously visited sites cannot be turned off. Chrome will also autocomplete the URLs of sites visited often.[29] If a user types keywords into the Omnibox that don't match any previously visited websites and presses 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 title bar. Like other browsers, it has a full-screen mode that hides the operating system and browser interface.

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, or Opera's Speed Dial.[29] In Google Chrome 2.0, the New Tab Page was updated to allow users to hide thumbnails they did not want to appear.[180]

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

File:Chrome Logo.svg
File:Google Chrome 2011 computer icon.svg
Google Chrome logos. Top: 3D motif from project start until March 2011. Bottom: 2D motif from March 2011 until present.

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.[182] As of 2009, this function was unavailable on the Linux and Mac platforms.[183]

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

Google Chrome's preferences page has four parts: Basic, Personal Stuff, Under the Hood, and, as of Chrome 15, a Downloads part. The Basic part includes options for the home page, search engine, and default browser. The Personal Stuff part lets users configure synchronization, saved passwords, form autofill, browsing data, and themes. The Under the Hood part allows changing network, privacy, download, and security settings. The Downloads part was a separate page at one time showing previous and active downloads but as of Chrome 15 is incorporated into Preferences.

Like Firefox, 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.[166]

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

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

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

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

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.[187][188]

Chrome Web Store

Main article: Chrome Web Store

Announced on December 7, 2010, the Chrome Web Store allows users to install web applications as extensions to the browser, although most of these function simply as links to popular web pages and/or games, but some of the apps like Springpad do provide extra features like offline access. The themes and extensions have also been tightly integrated into the new store, allowing users to search the entire catalog of Chrome extras.[189] The Chrome Web Store now acts as an App Store for Chromebooks.

The Chrome Web Store was opened on February 11, 2011 with the release of Google Chrome 9.0.[190]

Aero peek capability

Google has included aero peek capability for each tab on Windows 7. This is disabled by default due to performance issues,[191] but can be user enabled ,[192] resulting in a displayed thumbnail image of the tab. This creates similar functionality to IE 8, Firefox and other browsers.

Extensions

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

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

As of February 4, 2011, the extension gallery featured over 11500 extensions,[196] including official extensions from The Independent,[197] CEOP,[198] Transport for London,[199] Cricinfo,[200] WOT: Web of Trust[201] and FIFA.[202]

On October 2011, the Chrome webstore aka Extension gallery received a major upgrade, along with new extensions and better organization.[203]

Many Chrome extensions, once installed, have access to the user's data. There are three levels of permissions that an app or extension may request:[204]

  • High Alert - "plug-ins can do almost anything, in or outside of your browser. For example, they could use your webcam, or they could read your personal files."
  • Medium Alert - "This item can read every page that you visit -- your bank, your web email, your Facebook page, and so on." And, "Besides seeing all your pages, this item could use your credentials (cookies) to request or modify your data from websites."
  • Low Alert - "This item can read data that you copy into your operating system clipboard, which might include sensitive or private information." Among other things.

Many seemingly simple extensions, such Google's own Screen Capture Tool, require High Alert permissions.[205]

Themes

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

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

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.[210][211] 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.[212] 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.[213] 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.[214]

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

Platforms

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

  • Windows: XP Service Pack 2+ / Vista / 7, Intel Pentium 4 or later, 100 MB hard disk, 128 MB memory
  • Mac OS X: 10.5.6 or later, Intel (not PPC), 100 MB hard disk, 128 MB memory
  • Linux: Ubuntu 8.04 or later / Debian 5 / OpenSuse 11.1 , Intel Pentium 3 / Athlon 64 or later, 100 MB hard disk, 128 MB memory

As of 2012, 32-bit and 64-bit builds are available for Linux, with only 32-bit builds available for Mac OS X and Windows.[221][222]

Android version

A beta version for Android 4.0 devices was launched on February 7, 2012, available for a limited number of countries from the Android Market.[24]

  • Notable features: Synchronization with desktop Chrome to provide the same bookmarks and view the same browser tabs,[223] Page pre-rendering,[224] Hardware acceleration[225]
  • Many of the latest HTML5 features: almost all of the Web Platform’s features: GPU-accelerated canvas, including CSS 3D Transforms, CSS animations, SVG, WebSockets (including binary messages), Dedicated Workers; it has overflow scroll support, strong HTML5 video support, and new capabilities such as IndexedDB, WebWorkers, Application Cache and the File APIs, date and time pickers, parts of the Media Capture API.[224][226] Also supports mobile oriented features such as Device Orientation and Geolocation.[226]
  • Mobile customisations: Swipe gesture tab switching,[223] Link Preview allows zooming in on (multiple) links to ensure the desired one is clicked,[223] Font size boosting to ensure readability regardless of the zoom level[226]
  • Missing from the desktop version: no sandboxed tabs,[224][227] Safe Browsing[224], apps, or extensions[225] Adobe Flash (now and in future),[225] WebGL, Native Client[225]
  • Development changes: Remote debugging[224][228], part of the browser layer has been implemented in Java, communicating with the rest of the Chromium and WebKit code through Java Native Bindings.[226] The code of Chrome for Android is a fork of the Chromium project. It is a priority to upstream most new and modified code to Chromium and WebKit to resolve the fork[226]

Chrome OS

Main article: Google Chrome OS

Google Chrome is the basis of Google's Chrome OS operating system that ships on specific hardware from Google's manufacturing partners.[229] The user interface has a minimalist design resembling the Google Chrome browser. Chrome OS is aimed at users who spend most of their computer time on the Web; the only applications on the devices are a browser incorporating a media player and a file manager.[230][231][232][233][234]

Google announced Chrome OS on July 7, 2009.[235] Chromebooks from Acer and Samsung were launched in June and July 2011. A Chromebox from Samsung will be released in 2012.

Bundling

Chrome has been bundled with various Windows software installers, including Adobe Flash Player plug-in,[236] and pre-Microsoft owned Skype.[237]

Usage

Further information: Usage share of web browsers and Browser wars
Usage share of web browsers according to StatCounter, Chrome was 27.27% in October 2011.[9]

In 2008, The Daily Telegraph's Matthew Moore summarises 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."[238]

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".[239] 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."[240] 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 would not affect Google's revenue relationship with Mozilla.[241][242]

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 QuickLaunch 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[243]

As of January 2012, Chrome is the second most widely used browser, having overtaken Firefox in November 2011, with a 28.4% worldwide usage share of web browsers and is the most popular browser in Pakistan,[13] the Philippines,[244] Russia,[14] India,[12] and South America,[15] according to StatCounter.[9][11] According to StatCounter, Chrome was the most used web browser in Argentina, Chile, Uruguay, Philippines, Malaysia, Pakistan,Mauritania, Tunisia, Albania, Republic of Macedonia, Moldova, Jamaica and Armenia in July 2011.[9]

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". November 12, 2024. Retrieved November 12, 2024.
  2. ^ "Stable Channel Desktop Update". September 13, 2023. Retrieved September 14, 2023.
  3. ^ "Chrome Stable for iOS Update". November 12, 2024. Retrieved November 12, 2024.
  4. ^ "Extended Stable Channel Update for Desktop". November 12, 2024. Retrieved November 12, 2024.
  5. ^ "Chrome Beta for Desktop Update". November 13, 2024. Retrieved November 13, 2024.
  6. ^ "Chrome Beta for Android Update". November 6, 2024. Retrieved November 7, 2024.
  7. ^ "Chrome Beta for iOS Update". November 13, 2024. Retrieved November 13, 2024.
  8. ^ "Web Browser Market Share Trends". W3Counter. Awio Web Services LLC. Retrieved January 26, 2012.
  9. ^ a b c d e "Top 5 Browsers from December 2010 to December 2011". StatCounter. Retrieved January 8, 2012. Cite error: The named reference "StatsCounter" was defined multiple times with different content (see the help page).
  10. ^ "Web browsers (Global marketshare)". Clicky. Roxr Software Ltd. Retrieved September 29, 2011.
  11. ^ a b For additional sources see Usage share of web browsers#Summary table
  12. ^ a b Stats Counter Global Stats - Top 5 Browsers in India January 2012
  13. ^ a b "Top 5 browsers in Pakistan in Jan 2012". StatCounter. January 31, 2012. Retrieved February 3, 2012.
  14. ^ a b Stats Counter Global Stats - Top 5 Browsers in Russian Federation January 2012
  15. ^ a b Stats Counter Global Stats - Top 5 Browsers in South America December 2011
  16. ^ Ryan Paul (September 2, 2008). "Google unveils Chrome source code and Linux port". Ars Technica. Retrieved May 13, 2010.
  17. ^ "Google Chrome is built with open source code from Chromium." Retrieved from Chromium.org
  18. ^ "During a press briefing today, Google expressed hope that other browsers...". Retrieved from: Google unveils Chrome source code and Linux port, Ars Technica.
  19. ^ "Home (Chromium Developer Documentation)". Chromium Developer Documentation. dev.chromium.org. 2009. Retrieved May 5, 2009.
  20. ^ "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
  21. ^ "Chromium Terms and Conditions". Google Code. September 2, 2008. Retrieved September 3, 2008.
  22. ^ Chromium Project (2011). "ChromiumBrowserVsGoogleChrome". Retrieved July 10, 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  23. ^ McAllister, Neil (September 11, 2008). "Building Google Chrome: A first look". Fatal Exception. InfoWorld. Retrieved September 16, 2008. 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
  24. ^ a b "Google Chrome Beta arrives on Android". Gadgetnode.
  25. ^ Julia Angwin (July 9, 2009). "Sun Valley: Schmidt Didn't Want to Build Chrome Initially, He Says". WSJ Digits Blog. Retrieved May 25, 2010.
  26. ^ Scott McCloud (September 1, 2008). "Surprise!". Google Blogoscoped. Retrieved September 1, 2008.
  27. ^ Philipp Lenssen (September 1, 2008). "Google Chrome, Google's Browser Project". Retrieved September 1, 2008.
  28. ^ Philipp Lenssen (September 1, 2008). "Google on Google Chrome – comic book". Google Blogoscoped. Retrieved September 1, 2008.
  29. ^ a b c d e f g h i j k l m n o "Google Chrome". Google Book Search. September 1, 2008. Retrieved September 2, 2008.
  30. ^ a b Pichai, Sundar (September 1, 2008). "A fresh take on the browser". Google Blog. Retrieved September 1, 2008. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  31. ^ "It was when not if... Google Chrome". 2008. Retrieved September 2, 2008. {{cite web}}: Unknown parameter |month= ignored (help)
  32. ^ "Google Chrome update: First screenshot, and live-blog alert". CNet. September 1, 2008. Retrieved September 2, 2008.
  33. ^ "Google launches Chrome web browser". The Canadian Press. Associated Press. September 2, 2008. Retrieved September 2, 2008.
  34. ^ "Come on Google... Chrome for Mac?". 2008. Retrieved November 22, 2008. {{cite web}}: Unknown parameter |month= ignored (help)
  35. ^ Gruener, Wolfgang (January 3, 2009). "Google Chrome crosses 1% market share again". Chicago (IL): TG Daily. Retrieved January 3, 2009.
  36. ^ Shankland, Stephen (January 9, 2009). "Chrome gets Mac deadline, extensions foundation". CNET. Retrieved January 13, 2009.
  37. ^ "Early Access Release Channels".
  38. ^ "Danger: Mac and Linux builds available". Retrieved June 9, 2009.
  39. ^ Mark Larson (December 8, 2009). "Beta Update: Linux, Mac, and Windows". Google. Retrieved May 13, 2010.
  40. ^ a b "Google Chrome for the holidays: Mac, Linux and extensions in beta".
  41. ^ Brian Rakowski (May 25, 2010). "A new Chrome stable release: Welcome, Mac and Linux!". Google. Retrieved May 25, 2010.
  42. ^ "Microsoft offers browser choices to Europeans". BBC News. March 1, 2010. Retrieved May 13, 2010.
  43. ^ Peteris Krumins (September 5, 2008). "Code reuse in Google Chrome Browser". Retrieved May 13, 2010.
  44. ^ http://gs.statcounter.com/#browser-ww-monthly-200807-201106
  45. ^ Ian Fette (February 19, 2010). "Hello HTML5". Google. Retrieved May 24, 2010.
  46. ^ "HTML Video Codec Support in Chrome".
  47. ^ "Change MSI from a wrapper to "full" MSI".
  48. ^ Paul, Ryan (2010). "Google offering MSI to simplify Chrome enterprise deployment". Ars Technica. Retrieved December 16, 2010. {{cite news}}: Unknown parameter |month= ignored (help)
  49. ^ "Google Update for Enterprise".
  50. ^ "Windows Roaming Profile support".
  51. ^ Kevin Purdy. "Chrome Canary Build Provides Bleeding-Edge Updates Alongside Stable Chrome". Lifehacker.com.
  52. ^ "Google Chrome, Chromium, and Google". blog.chromium.org/. The Chromium Blog. 2008. Retrieved February 17, 2010.
  53. ^ "Differences between Google Chrome and Linux distro Chromium". Google /. 2010. Retrieved 2010-09=01. {{cite web}}: Check date values in: |accessdate= (help)
  54. ^ a b c Google (2010). "In The Open, For RLZ". Retrieved June 20, 2010. {{cite web}}: |last= has generic name (help); Unknown parameter |month= ignored (help)
  55. ^ Keizer, Gregg (2011). "Microsoft kills Google Chrome with bad malware signature". Computerworld. Retrieved October 1, 2011. {{cite news}}: Unknown parameter |month= ignored (help)
  56. ^ Bott, Ed (2011). "Users report Microsoft Security Essentials removes Google Chrome". ZDNet. Retrieved October 1, 2011. {{cite news}}: Unknown parameter |month= ignored (help)
  57. ^ Metz, Cade (2011). "Microsoft Anti-Malware Tool Mistakenly Snuffs Google Chrome". Wired. Retrieved October 1, 2011. {{cite news}}: Unknown parameter |month= ignored (help)
  58. ^ Sampson, Ted (2011). "Microsoft security update treats Chrome as malware". InfoWorld. Retrieved October 1, 2011. {{cite news}}: Unknown parameter |month= ignored (help)
  59. ^ "Google downgrades Chrome ranking after paid-link monkey business". ComputerWorld. January 4, 2012. Retrieved February 4, 2012.
  60. ^ Chrome Beta, Market.android.com, retrieved February 9, 2012
  61. ^ Install Chrome for Android Beta, Support.google.com, retrieved February 9, 2012
  62. ^ Sundar Pichai, Google Chrome Blog: Introducing Chrome for Android, Chrome.blogspot.com, retrieved February 9, 2012
  63. ^ The Chromium Blog: A deeper look at Chrome for Android, Blog.chromium.org, retrieved February 9, 2012
  64. ^ Chrome for Android Beta, Market.android.com, retrieved February 9, 2012
  65. ^ "Release Notes". The Chromium Projects.
  66. ^ "ChangeLog – v8".
  67. ^ "A Fresh take on the browser". September 1, 2008. Retrieved March 20, 2011.
  68. ^ "Google Chrome Releases: Stable Update: Google Chrome 2.0.172.28".
  69. ^ "Google Chrome Releases: Stable Channel Update".
  70. ^ Google Chrome Releases: Stable Channel Update March 17, 2010
  71. ^ Brian Rakowski (May 25, 2010). "Evolving from beta to stable with a faster version of Chrome". Google. Retrieved May 25, 2010.
  72. ^ "Adobe Flash Player support now enabled in Google Chrome's stable channel". June 30, 2010. Retrieved August 8, 2010.
  73. ^ "Bringing improved PDF support to Google Chrome". Chromium Blog. June 17, 2010. Retrieved October 24, 2010.
  74. ^ "Bringing another Chrome release to you, right on time". Google. Retrieved October 24, 2010.
  75. ^ "Stable, Beta Channel Updates". Google. Retrieved December 3, 2010.
  76. ^ "Safer plug-ins, faster search, and richer graphics". Google. Retrieved December 17, 2010.
  77. ^ "WebP Home". Google. Retrieved February 3, 2011.
  78. ^ "Dev Channel Update". Google. Retrieved January 21, 2011.
  79. ^ "Dev Channel Update". Google. Retrieved January 21, 2011.
  80. ^ "Issue 48607: Sandbox GPU process".
  81. ^ "A New Crankshaft for V8". Google. Retrieved December 17, 2010.
  82. ^ "A New Crankshaft for V8". Google. Retrieved December 17, 2010.
  83. ^ "Chrome Beta Release". March 22, 2011. Retrieved March 23, 2011.
  84. ^ a b Rura, Steve (2011). "A fresh take on an icon". Retrieved March 22, 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  85. ^ a b "Chrome Stable Release". June 7, 2011. Retrieved June 7, 2011.
  86. ^ Google Operating System: Chrome shifts into a new gear, Google Operating System (Unofficial Google Blog), June 7, 2011, retrieved February 4, 2012
  87. ^ Bentzel, Chris (June 16, 2011). "Google Chrome Blog: Faster than fast". chrome.blogspot.com. Retrieved August 21, 2011.
  88. ^ "Building better web apps with a new Chrome Beta". Retrieved August 15, 2011.
  89. ^ "Chrome Beta Channel Update". Retrieved August 15, 2011.
  90. ^ "ImperialViolet". Retrieved August 17, 2011.
  91. ^ a b c "Download Google Chrome 15.0.874.15 Dev with Fixes for the Revamped New Tab Page". Retrieved September 19, 2011.
  92. ^ a b "Download Google Chrome 16 Dev and Chrome 15 Beta". Retrieved September 23, 2011.
  93. ^ "Switch Chromium to ffmpeg native vp8 decoder".
  94. ^ Chromium Issue 48119: Feature request: optional permissions in Chrome extensions, Google Code, July 1, 2010, retrieved February 4, 2012
  95. ^ Chromium Issue 99332: Remove sidetabs, Google Code, October 6, 2011, retrieved February 4, 2012
  96. ^ a b c d "Stable Channel Update". Retrieved February 9, 2012.
  97. ^ "Google Chrome 17 FINAL". Retrieved February 9, 2012.
  98. ^ "Chrome Releases: Dev Channel Update". Google Chrome Releases. February 10, 2012. Retrieved February 18, 2012.
  99. ^ "Technology overview – Google chrome".
  100. ^ Gloson (December 4, 2008). "Google Chrome's Unique Features". Retrieved May 13, 2010.
  101. ^ [1] Chromium issue tracker
  102. ^ Stephen Shankland (September 2, 2008). "Speed test: Google Chrome beats Firefox, IE, Safari – Business Tech". CNET News. Retrieved May 13, 2010.
  103. ^ Kevin Purdy (June 11, 2009). "Lifehacker Speed Tests: Safari 4, Chrome 2, and More – Browsers". Lifehacker. Retrieved May 13, 2010.
  104. ^ 12 Unique features of Google Chrome, TechStroke
  105. ^ Rafe Needleman (May 14, 2008). "The future of the Firefox address bar". CNET News. Retrieved May 13, 2010.
  106. ^ Anthony Laforge. Stable Channel Update "Stable Channel Update". Google. Retrieved May 25, 2010. {{cite web}}: Check |url= value (help)
  107. ^ "ECMAScript test262". ECMAScript. Retrieved May 6, 2011.
  108. ^ "CSS 2.1 Test Suite RC6 Results". W3C. Retrieved May 6, 2011.
  109. ^ "HTML5 test". Chrome. Retrieved January 2, 2012.
  110. ^ Chung, Marc (September 5, 2008). "chromes-process model explained". Retrieved September 10, 2008.
  111. ^ Google (September 1, 2008). "Google Chrome". Retrieved September 3, 2008. {{cite web}}: |author= has generic name (help)[dead link‍]
  112. ^ Barth, Adam. "The Security Architecture of the Chromium Browser" (PDF). Stanford Security Laboratory. Retrieved September 11, 2008. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  113. ^ Markus Gutschke (May 6, 2009). "Re: [[PATCH 2/2]] x86-64: seccomp: fix 32/64 syscall hole". Retrieved February 17, 2011. {{cite web}}: URL–wikilink conflict (help)
  114. ^ Jake Edge (August 19, 2009). "Google's Chromium sandbox". Retrieved February 17, 2011.
  115. ^ a b "Google Chrome FAQ for web developers".
  116. ^ Paul, Ryan (2010). "Google bakes Flash into Chrome, hopes to improve plug-in API". Retrieved March 14, 2010. {{cite web}}: Unknown parameter |month= ignored (help)
  117. ^ "Java and Google Chrome". Java.com. Retrieved December 11, 2009.
  118. ^ "Issue 10812 – chromium – No java plugin support yet". Google. Retrieved May 18, 2010.
  119. ^ Gregg Keizer, Google's Chrome untouched at Pwn2Own hack match, Computerworld, March 10, 2011
  120. ^ Pwn2Own 2012: Google Chrome browser sandbox first to fall
  121. ^ CanSecWest Pwnium: Google Chrome hacked with sandbox bypass
  122. ^ Teenager hacks Google Chrome with three 0day vulnerabilities
  123. ^ Kersey, Jason (March 10, 2012). "Chrome Stable Update". Retrieved March 10, 2012.
  124. ^ Hughes, Brian. "Virus Bulletin : 2010 - Social engineering trumps a zero-day every time". AVG Technologies. Retrieved July 21, 2011.
  125. ^ Bright, Peter (July 16, 2011). "Internet Explorer 9 utterly dominates malware-blocking stats". Ars Technica. Retrieved July 16, 2011.
  126. ^ "Web Browser Group Test Socially-Engineered Malware". NSS Labs. July 16, 2011.
  127. ^ "Explore Google Chrome Features: Incognito Mode". September 2, 2008. Retrieved September 4, 2008.
  128. ^ "Communications between Chromium/Google Chrome and service providers".
  129. ^ a b "SRWare Iron webpage". Retrieved October 12, 2008.
  130. ^ a b c d "Google Chrome Privacy Whitepaper" (PDF).
  131. ^ "&rlz= in Google referrer: Organic traffic or AdWords?". Retrieved February 27, 2009.
  132. ^ a b c "Google Reacts to Some Chrome Privacy Concerns". Retrieved September 24, 2008.
  133. ^ a b Controlled by the setting "Send usage statistics and error reports". Default off.
  134. ^ Google Chrome Privacy Notice, Google.com, December 13, 2011, retrieved February 4, 2012
  135. ^ "Google Chrome Unique Identifier Change". March 16, 2010. Retrieved March 24, 2010.
  136. ^ Ackerman, Elise. "Google browser's tracking feature alarms developers, privacy advocates". Mercury News.
  137. ^ "Google's Omnibox could be Pandora's box". September 3, 2008. Retrieved September 4, 2008.
  138. ^ "Be sure to read Chrome's fine print". CNET. Retrieved September 3, 2008.
  139. ^ "Google Terms of Service".
  140. ^ "Google Chrome Terms of Service (English)". Retrieved September 4, 2008.
  141. ^ "Google Amends Chrome License Agreement After Objections" (Document). PC World. September 3, 2008. {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)
  142. ^ "Google Chrome Privacy Notice". Retrieved October 27, 2009.
  143. ^ Fried, Ina (September 3, 2008). "Google's Omnibox could be Pandora's box". Retrieved May 13, 2010.
  144. ^ Bakke, Kurt (2011). "Chrome Shields Websites From Denial-Of-Service Attacks". Conceivably Tech. Retrieved April 20, 2011. {{cite news}}: Unknown parameter |month= ignored (help)
  145. ^ Bakke, Kurt (2011). "Google Menu Ad Tracking: A Case Of Bad Timing?". Conceivably Tech. Retrieved April 20, 2011. {{cite news}}: Unknown parameter |month= ignored (help)
  146. ^ Dotzler, Asa (2011). "Chrome, Do Not Track, and Google Advertising". Retrieved April 20, 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  147. ^ "Keep My Opt-Outs, Chrome Web Store". Retrieved June 19, 2011.
  148. ^ Thurrott, Paul (2011). "Daily Update: Google's Do Not Track Solution, Apple Stuff, Crysis 2 Demo, More". Retrieved April 22, 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  149. ^ "Google and Chrome To Support Do Not Track". Retrieved March 3, 2012.
  150. ^ "V8 Benchmark suite". Google code. Retrieved September 3, 2008.
  151. ^ Rupert Goodwins (September 2, 2008). "Google Chrome – first benchmarks. Summary: wow". Retrieved September 3, 2008.
  152. ^ "Google Chrome Javascript Benchmarks". September 2, 2008. Retrieved September 3, 2008. [dead link‍]
  153. ^ Adrian Kingsley-Hughes (September 2, 2008). "Google Chrome is insanely fast ... faster than Firefox 3.0". Retrieved September 3, 2008.
  154. ^ Stephen Shankland (September 2, 2008). "Speed test: Google Chrome". CNET Business Tech. Retrieved September 3, 2008.
  155. ^ Alexander Limi (September 2, 2008). "Chrome: Benchmarks and more". Retrieved May 13, 2010.
  156. ^ Vygantas Lipskas (March 1, 2009). "Safari 4 vs. Firefox 3 vs. Google Chrome vs. Opera 10, 9.6 vs. Internet Explorer 8, 7". Favbrowser. Retrieved May 13, 2010.
  157. ^ Scott M. Fulton, III (October 11, 2010). "Firefox in the dust: Opera poised to reclaim browser performance lead". Retrieved November 6, 2010.
  158. ^ Stephen Shankland (September 3, 2008). "Firefox counters Google's browser speed test – Business Tech". CNET News. Retrieved May 13, 2010.
  159. ^ Eich, Brendan (September 3, 2008). "TraceMonkey Update". Retrieved September 3, 2008.
  160. ^ Stephen Shankland (November 3, 2008). "Third Chrome beta another notch faster – News". Builder AU. Retrieved May 13, 2010.
  161. ^ Resig, John (September 3, 2008). "JavaScript Performance Rundown". Retrieved June 9, 2008.
  162. ^ Maciej Stachowiak (September 18, 2008). "WebKit blog: Introducing SquirrelFish Extreme". Retrieved May 13, 2010.
  163. ^ Cameron Zwarich (September 18, 2008). "SquirrelFish Extreme has landed!". Retrieved May 13, 2010.
  164. ^ Stephen Shankland (September 22, 2008). "Step aside, Chrome, for Squirrelfish Extreme – News". Builder AU. Retrieved May 13, 2010.
  165. ^ Charles Ying (September 19, 2008). "SquirrelFish Extreme: Fastest JavaScript Engine Yet". Retrieved May 13, 2010.
  166. ^ a b Preston Gralla (September 3, 2008). "Three hidden Chrome features you'll love". Retrieved September 16, 2008.
  167. ^ "DNS prefetching for Firefox". November 8, 2008.
  168. ^ Apple Inc. (June 7, 2010). "What's new in Safari 5". Retrieved July 6, 2010.
  169. ^ Internet Explorer 9 Network Performance Improvements
  170. ^ Page prefetcher
  171. ^ "Chromium SPDY client implementation".
  172. ^ "Chromium: SPDY proxy examples".
  173. ^ "spdy-dev mailing list: SPDY on Google servers?".
  174. ^ Reisn, Charlie (September 11, 2008). "Multi-process Architecture". Retrieved September 12, 2008.
  175. ^ "Process Models". The Chromium Projects. Google. September 3, 2008. Retrieved September 12, 2008.
  176. ^ Prince, Brian (December 11, 2008). "Google Chrome Puts Security in a Sandbox". eWeek.com. Ziff Davis Enterprise Holdings Inc. Retrieved June 4, 2010.
  177. ^ "Google Chrome book". Google. September 21, 2008. Retrieved September 21, 2008.
  178. ^ "Webkit.org".
  179. ^ "Firefox Lorentz beta available for download and testing". Mozilla. April 8, 2010.
  180. ^ "A Speedier Google Chrome for all users". Google Chrome Blog.
  181. ^ Anthony Laforge (September 15, 2009). "Google Chrome after a year: Sporting a new stable release". Google. Retrieved May 13, 2010.
  182. ^ Kevin Purdy (September 2, 2009). "Add a Bookmark Button to Google Chrome's Toolbar". Lifehacker. Retrieved May 13, 2010.
  183. ^ Google (2009). "Issue 21152: Expose UI for bookmark menu on all platforms". Retrieved December 30, 2009. {{cite web}}: |last= has generic name (help); Unknown parameter |month= ignored (help)
  184. ^ "Google Chrome with 3D". Google. April 1, 2009. Retrieved May 26, 2009.
  185. ^ "Chromium url_constants.cc". Retrieved September 1, 2010.
  186. ^ Pash, Adam (2010). "Chrome's About:Labs Renamed to About:Flags, Adds a Warning". LifeHacker. Retrieved October 19, 2010. {{cite news}}: Unknown parameter |month= ignored (help)
  187. ^ "Chrome Web Store". Google. May 19, 2010. Retrieved May 24, 2010.
  188. ^ Erik Lay (May 19, 2010). "The Chrome Web Store". Google. Retrieved May 24, 2010.
  189. ^ Paul, Ryan (2010). "Chrome Web Store: a solution in search of a problem?". Ars Technica. Retrieved December 10, 2010. {{cite news}}: Unknown parameter |month= ignored (help)
  190. ^ Google (2011). "A dash of speed, 3D and apps". Retrieved February 7, 2011. {{cite web}}: |last= has generic name (help); Unknown parameter |month= ignored (help)
  191. ^ "Issue 37957: Investigate solutions for Aero Peek flooding users with tab thumbnails".
  192. ^ "Issue 8036: Show thumbnails for open tabs on Windows 7 superbar (Aero Peek)".
  193. ^ Aaron Boodman (September 9, 2009). "Extensions Status: On the Runway, Getting Ready for Take-Off". Google. Retrieved May 13, 2010.
  194. ^ Erik Kay (December 8, 2009). "Extensions beta launched, with over 300 extensions!". Google. Retrieved May 13, 2010.
  195. ^ Nick Baum (January 25, 2010). "Over 1,500 new features for Google Chrome". Google Chrome Blog. Retrieved May 13, 2010.
  196. ^ "Security improvements and registration updates for the Google Chrome Extensions Gallery". August 19, 2010.
  197. ^ "Official Independent Chrome Extension".
  198. ^ "CEOP Official Chrome Extension".
  199. ^ "Official TfL Chrome Extension".
  200. ^ "ESPN Cricinfo".
  201. ^ "WOT – Google Chrome extension gallery".
  202. ^ "Official World Cup FIFA Chrome Extension".
  203. ^ Shannon Guymon (October 25, 2011). "Making Chrome even more app-ealing". Google Chrome Blog. Retrieved October 25, 2011.
  204. ^ Chrome Web Store Help
  205. ^ Screen Capture Tool
  206. ^ Glen Murphy (October 5, 2009). "A splash of color to your browser: Artist Themes for Google Chrome". Google Chrome Blog. Retrieved May 13, 2010.
  207. ^ "Google Chrome Themes Gallery".
  208. ^ Basic settings: Change browser theme Google Chrome Help
  209. ^ "Support Google Chrome – Automatic web page translation".
  210. ^ Mark Larson (January 8, 2009). "Google Chrome Release Channels". Retrieved January 9, 2009.
  211. ^ Mark Larson (January 8, 2009). "Dev update: New WebKit version, new features, and a new Dev channel". Retrieved January 9, 2009.
  212. ^ Anthony Laforge (July 22, 2010). "Release Early, Release Often". Retrieved July 25, 2010.
  213. ^ Lee Mathews (July 23, 2010). "Google drops Chrome Canary build down the Chrome mineshaft". Retrieved July 25, 2010.
  214. ^ Adding more yellow to the Mac color scheme, Blog.chromium.org, May 2, 2011, retrieved February 4, 2012
  215. ^ David Dorwin (May 14, 2009). "Google Update Releases Update Controls". Retrieved May 13, 2010.
  216. ^ "standalone download page".
  217. ^ Alex Chitu (March 1, 2009). "Standalone Offline Installer for Google Chrome". Google Operating System. Retrieved May 13, 2010.
  218. ^ "Google Help page "Managing updates in Google Software Update"".
  219. ^ Stephen Adams (July 15, 2009). "Chromium Blog: Smaller is Faster (and Safer Too)". Retrieved May 13, 2010.
  220. ^ Google. "System requirements : Install or update Google Chrome : Google Chrome Help". Retrieved April 8, 2011. {{cite web}}: |author= has generic name (help)
  221. ^ Google. "64-bit Support – The Chromium Projects". Retrieved March 5, 2012. {{cite web}}: |author= has generic name (help)
  222. ^ Google. "Google Chrome for Linux – Terms and Conditions Agreement". Retrieved April 8, 2011. {{cite web}}: |author= has generic name (help)
  223. ^ a b c Beta version of Chrome for Android 4.0 released, Neowin.net, retrieved February 9, 2012
  224. ^ a b c d e Google Operating System: Chrome for Android, Googlesystem.blogspot.com, February 27, 2004, retrieved February 9, 2012
  225. ^ a b c d Google Chrome for Android – 23 Questions and Answers, Chromestory.com, retrieved February 9, 2012
  226. ^ a b c d e Bringing Google Chrome to Android, Peter.sh, January 30, 2012, retrieved February 9, 2012
  227. ^ Security overview, Support.google.com, retrieved February 9, 2012
  228. ^ Google Chrome for Android: Remote Debugging, Code.google.com, retrieved February 9, 2012
  229. ^ Dylan F. Tweney (November 19, 2009). "Gadget Lab Hardware News and Reviews Google Chrome OS: Ditch Your Hard Drives, the Future Is the Web". Wired. Retrieved November 22, 2009.
  230. ^ Sengupta, Caesar (November 19, 2009). "Releasing the Chromium OS open source project". Official Google Blog. Google, Inc. Retrieved November 19, 2009.
  231. ^ Stokes, Jon (January 19, 2010). "Google talks Chrome OS, HTML5, and the future of software". Ars Technica. Retrieved January 23, 2010.
  232. ^ Womack, Brian (July 8, 2009). "Google to Challenge Microsoft With Operating System". Bloomberg. Retrieved July 8, 2009.
  233. ^ Hansell, Saul (July 8, 2009). "Would you miss Windows with a Google operating system?". New York Times. Retrieved July 8, 2009.
  234. ^ Pichai, Sundar (July 7, 2009). "Introducing the Google Chrome OS". Official Google Blog. Google, Inc. Retrieved July 16, 2009.
  235. ^ Mediati, Nick (July 7, 2009). "Google Announces Chrome OS". PC World. Retrieved July 8, 2009.
  236. ^ "Wonder How Chrome is Growing Market Share? Ask Adobe".
  237. ^ Brinkmann, Martin (October 16, 2011). "Skype Update Removes Google Product Bundling". Martin Brinkmann. Retrieved July 8, 2009.
  238. ^ Moore, Matthew (September 2, 2008). "Google Chrome browser: Review of reviews". Daily Telegraph. Retrieved September 24, 2011.
  239. ^ Liedtke, Michael (September 3, 2008). "Google polishes product line with Chrome browser" (Document). {{cite document}}: Cite document requires |publisher= (help); Unknown parameter |agency= ignored (help); Unknown parameter |url= ignored (help)
  240. ^ Jaroslovsky, Rich (February 25, 2010). "Browser Wars: The Sequel" (Document). {{cite document}}: Cite document requires |publisher= (help); Unknown parameter |url= ignored (help); Unknown parameter |work= ignored (help)
  241. ^ "Thoughts on Chrome & More". John's Blog. September 1, 2008. Retrieved May 13, 2010.
  242. ^ Collins, Barry (September 2, 2008). "Mozilla: Google's not trying to kill us" (Document). PC Pro. {{cite document}}: Unknown parameter |url= ignored (help)
  243. ^ Mediati, Nick (September 3, 2008). "Google Chrome Web Browser". PC World. Retrieved September 7, 2008. {{cite web}}: Check date values in: |date= (help)
  244. ^ "Top 5 browsers in Philippians in Jan 2012". StatCounter. January 31, 2012. Retrieved February 3, 2012.
Wikimedia Commons has media related to Google Chrome.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Google_Chrome&oldid=481534324"