Jump to content

Google Chrome: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Line 75: Line 75:
Google created [[Gears (software)|Gears]] for Chrome, which added features for [[web developer]]s typically relating to the building of web applications, including offline support.<ref name="chrome-comic"/> However, Google phased out Gears in favor of [[HTML5]].<ref>{{cite web |url= http://gearsblog.blogspot.com/2010/02/hello-html5.html |title= Hello HTML5 |publisher=Google |author=Ian Fette |date= February 19, 2010 |accessdate=2012-07-11}}</ref>
Google created [[Gears (software)|Gears]] for Chrome, which added features for [[web developer]]s typically relating to the building of web applications, including offline support.<ref name="chrome-comic"/> However, Google phased out Gears in favor of [[HTML5]].<ref>{{cite web |url= http://gearsblog.blogspot.com/2010/02/hello-html5.html |title= Hello HTML5 |publisher=Google |author=Ian Fette |date= February 19, 2010 |accessdate=2012-07-11}}</ref>


On January 11, 2011 the Chrome product manager, Mike Jazayeri, announced that Chrome would remove [[H.264/MPEG-4 AVC|H.264 video codec]] support for its HTML5 player, citing the desire to bring Google Chrome more in line with the currently available open codecs available in the Chromium project, which Chrome is based on.<ref>{{cite web|url=http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html |title=HTML Video Codec Support in Chrome |publisher=blog.chromium.org |date=January 11, 2011 |accessdate=April 8, 2012}}</ref> Despite this, on November 6, 2012, Google released a version of Chrome on Windows which added [[Hardware acceleration|hardware-accelerated]] H.264 video decoding.<ref>{{cite web|url=http://chrome.blogspot.com/2012/11/longer-battery-life-and-easier-website.html |title=Longer battery life and easier website permissions |publisher=chrome.blogspot.com |date=November 6, 2012 |accessdate=December 3, 2012}}</ref> As of December 2012, there has been no further announcement about the future of Chrome H.264 support.
On January 11, 2011 the Chrome product manager, Mike Jazayeri, announced that Chrome would remove [[H.264/MPEG-4 AVC|H.264 video codec]] support for its HTML5 player, citing the desire to bring Google Chrome more in line with the currently available open codecs available in the Chromium project, which Chrome is based on.<ref>{{cite web|url=http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html |title=HTML Video Codec Support in Chrome |publisher=blog.chromium.org |date=January 11, 2011 |accessdate=April 8, 2012}}</ref> Despite this, on November 6, 2012, Google released a version of Chrome on Windows which added [[Hardware acceleration|hardware-accelerated]] H.264 video decoding.<ref>{{cite web|url=http://chrome.blogspot.com/2012/11/longer-battery-life-and-easier-website.html |title=Longer battery life and easier website permissions |publisher=chrome.blogspot.com |date=November 6, 2012 |accessdate=December 3, 2012}}</ref> As of December 2012, there has been no further announcement about the future of Chrome H.264 support. Most of all, there are lots of gays here in Somewhere. It is also ah country problem because of their capabilities.


On February 7, 2012, Google launched ''Google Chrome Beta'' for [[Android 4.0]] (Ice Cream Sandwich) devices.<ref name="engadget">{{cite news|url=http://www.engadget.com/2012/02/07/google-chrome-browser-arrives-on-android-video/|title=Google Chrome Beta arrives on Android|publisher=Engadget|accessdate=2012‑07‑11}}</ref> On new devices with [[Jelly Bean (operating system)|Jelly Bean]] preinstalled, Chrome is the default browser.<ref>[http://www.muktware.com/3779/chrome-out-beta-default-browser-android-41 "Chrome Out Of Beta, Default Browser Of Android 4.1"]. Muktware.com. June 28, 2012. Retrieved September 15, 2012.</ref>
On February 7, 2012, Google launched ''Google Chrome Beta'' for [[Android 4.0]] (Ice Cream Sandwich) devices.<ref name="engadget">{{cite news|url=http://www.engadget.com/2012/02/07/google-chrome-browser-arrives-on-android-video/|title=Google Chrome Beta arrives on Android|publisher=Engadget|accessdate=2012‑07‑11}}</ref> On new devices with [[Jelly Bean (operating system)|Jelly Bean]] preinstalled, Chrome is the default browser.<ref>[http://www.muktware.com/3779/chrome-out-beta-default-browser-android-41 "Chrome Out Of Beta, Default Browser Of Android 4.1"]. Muktware.com. June 28, 2012. Retrieved September 15, 2012.</ref>

Revision as of 08:03, 8 January 2013

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 (2008-09-02)
Stable release
Windows, macOS, Linux130.0.6723.91/92[1] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)
Windows Server 2012/2012 R2109.0.5414.165[2] / 13 September 2023; 13 months ago (2023-09-13)
Android130.0.6723.86[3] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)
iOS, iPadOS130.0.6723.90[4] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)
Extended Support Release130.0.6723.92[1] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)

Mobile versions:
Template:Latest stable software release/Google Chrome for Android
Windows, macOS, Linux130.0.6723.91/92[1] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)
Windows Server 2012/2012 R2109.0.5414.165[5] / 13 September 2023; 13 months ago (2023-09-13)
Android130.0.6723.86[3] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)
iOS, iPadOS130.0.6723.90[4] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)
Extended Support Release130.0.6723.92[1] Edit this on Wikidata / 29 October 2024; 4 days ago (29 October 2024)

Preview release
Windows, macOS, Linux131.0.6778.24[6] Edit this on Wikidata / 30 October 2024; 3 days ago (30 October 2024)
Android131.0.6778.22[7] Edit this on Wikidata / 30 October 2024; 3 days ago (30 October 2024)
iOS, iPadOS131.0.6778.22[8] Edit this on Wikidata / 30 October 2024; 3 days ago (30 October 2024)
Written inC++, assembly, Python, JavaScript
EngineWebKit, V8 JavaScript engine
Operating systemAndroid (4.0 and later)
iOS (4.3 or later)
Linux
OS X (10.6 and later)
Windows (XP SP2 and later)
Available in50 languages
TypeWeb browser, mobile web browser
LicenseFreeware under Google Chrome Terms of Service[9][note 1]
Websitewww.google.com/chrome

Google Chrome is a freeware web browser[9] developed by Google that uses the WebKit layout engine. It was released as a beta version for Microsoft Windows on September 2, 2008, and as a stable public release on December 11, 2008. As of November 2012, according to StatCounter, Google Chrome had 35% worldwide usage share of web browsers making it the most widely used web browser.[10] Net Applications, however, indicates that Chrome is only third when it comes to the size of its user base, behind Internet Explorer and Firefox.[11]

In September 2008, Google released a large portion of Chrome's source code as an open source project called Chromium,[12][13] on which Chrome releases are still based.

History

Google's Eric Schmidt opposed the development of an independent web browser for six years. He stated that "at the time, Google was a small company", and he did not want to go through "bruising browser wars". After co-founders Sergey Brin and Larry Page hired several Mozilla Firefox developers and built a demonstration of Chrome, however, Schmidt admitted that "It was so good that it essentially forced me to change my mind".[14]

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

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

On the same day, a CNET news item[21] 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. This passage was inherited from the general Google terms of service.[22] Google responded to this criticism immediately by stating that the language used was borrowed from other products, and removed this passage from the Terms of Service.[23]

Chrome quickly gained about 1% usage share.[19][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 OS X and Linux developer previews[29] were announced on June 4, 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 May 25, 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

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 V8 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.

Web browser statistics on Wikimedia
Chrome
 
 30.60%
I.E.
 
 22.01%
Firefox
 
 19.11%
Safari
 
 15.15%
Android
 
 4.26%
Opera
 
 4.37%
Other
 
 4.50%
Web browser usage for Wikimedia visitors as of October 2012.[36] I.E. = Internet Explorer.

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

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

On January 11, 2011 the Chrome product manager, Mike Jazayeri, announced that Chrome would remove H.264 video codec support for its HTML5 player, citing the desire to bring Google Chrome more in line with the currently available open codecs available in the Chromium project, which Chrome is based on.[38] Despite this, on November 6, 2012, Google released a version of Chrome on Windows which added hardware-accelerated H.264 video decoding.[39] As of December 2012, there has been no further announcement about the future of Chrome H.264 support. Most of all, there are lots of gays here in Somewhere. It is also ah country problem because of their capabilities.

On February 7, 2012, Google launched Google Chrome Beta for Android 4.0 (Ice Cream Sandwich) devices.[40] On new devices with Jelly Bean preinstalled, Chrome is the default browser.[41]

Windows 8 mode

File:Google Chrome Windows 8 Mode.jpg
Google Chrome in Windows 8 Mode

In March 2012 Google announced the development of a version of Chrome for both the Metro and desktop versions of Windows 8.[42] After the release of Windows 8, a new version of the browser was released to work with the Microsoft Metro/Modern design. The browser can be run on both Desktop and Metro version. The title-bar changes to black when it is switched to Windows 8 mode. The default built-in (PPAPI) Flash Player Plugin runs in Windows 8 mode.[citation needed]

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 (.mst), but the provided MSI is only a very limiting MSI wrapper around the normal installer that does not fulfill enterprise needs.[43] 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[44] — 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.[45] Until version 22 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.[46]

Chromium

Main article: Chromium (web browser)

In September 2008, Google released a large portion of Chrome's source code as an open source project called Chromium. This move enabled third-party developers to study the underlying source code and to help port the browser to the Mac OS X and Linux operating systems. The Google-authored portion of Chromium is released under the permissive BSD license.[47] Other portions of the source code are subject to a variety of open source licenses.[48] Chromium is similar to Chrome, but lacks built-in automatic updates, built-in PDF reader and built-in Flash player, as well as Google branding and has a blue-colored logo instead of the multicolored Google logo.[49][50] Chromium does not implement user RLZ tracking.[51][52][53]

Release history

Click "show" to expand the release history table below.

Release history

Legend:

Color Meaning
Red Old release
Green Stable release
Blue Beta release
Purple Dev release
Major version Release date WebKit version[54] V8 engine version[55] 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.
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 auto-fill.
  • Sort bookmarks by title.
  • Tab docking to browser and desktop edges.
  • Basic Greasemonkey support.[57]
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.
  • Experimental new anti-reflected-XSS feature called "XSS Auditor".[58]
4.1.249 2010-03-17
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 auto-fill.
  • Expanded synchronization support to include extensions and auto-fill data.
  • Support for WebM videos.
  • Built-in PDF support (disabled by default).[62]
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.[63]
  • 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.[64]
  • This release added "about:flags" to showcase experimental features such as Chrome Instant, side tabs on Windows, tabbed settings, Click to Play [clarification needed], background web applications, Remoting [clarification needed], Disable outdated plug-ins [clarification needed], XSS Auditor [clarification needed], Cloud Print Proxy [clarification needed], 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 (a la Google Instant) option.[65]
  • WebP support.[66]
  • 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.[67][68]
  • Faster JavaScript performance due to incorporation of Crankshaft, an improved compiler for V8.[69]
  • 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.[70]
11.0.696 2011-04-27 534.24 3.1.8.16
  • HTML5 Speech Input API.[71]
  • Updated icon.[72]
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.[73]
  • 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.[73]
  • 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.[74]
13.0.782 2011-08-02 535.1 3.3.10.30
  • Instant Pages (pre-rendering of Web pages).[75]
  • Native print interface and preview (Linux and Windows only).
  • Experimental new tab page.
  • Experimental Restrict Instant To Search option.
14.0.835 2011-09-16 3.4.14.21
  • Native Client (NaCl) enabled for apps in the Chrome Web Store.[76]
  • Web Audio API.
  • Additional Mac OS X Lion feature support.
  • Sync Encryption for all data.
  • Print preview on Mac.
  • Validation of HTTPS sites.[77]
  • Experimental Web Request extension API.
  • Experimental Content Settings extension API.[78]
15.0.874 2011-10-25 535.2 3.5.10.24
  • Faster print preview.[79]
  • Redesigned new tab page on by default.[79]
  • JavaScript fullscreen API enabled by default.[79]
  • Inline installation of Chrome Web Store items by verified sites.
  • Omnibox History synchronization.[80]
  • Switched to FFmpeg native VP8 decoder.[81]
  • 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.[80]
  • Optional permissions in Chrome extensions, so the user can opt-in or opt-out of the optional permissions at installation time.[82]
  • Experimental support for side tabs was removed.[83]
17.0.963 2012-02-08 535.11 3.7.12.29
  • Updated Omnibox prerendering of pages.[84]
  • Download scanning protection.[84]
  • New extensions APIs.[84]
  • Improved History tab.
  • Removal of "+" symbol from the "new tab" button.
  • Added limited support for changing user agent strings.
  • Adjustable margins in print preview.[85]
  • Search engine synchronization.[86]
  • Disabled GAIA profile info.[87]
18.0.1025 2012-03-28 535.19 3.8.9.19
  • Hardware-accelerated Canvas2D graphics.[88]
  • WebGL without the need of 3D graphics hardware through the software rasterizer SwiftShader.[88]
  • Brighter "new tab" button.[89]
19.0.1084 2012-05-15 536.5 3.9.24.7
  • Access tabs between devices.[90]
  • Reorganized and searchable settings interface.
  • Added better spell check by using the Google search engine spell checker.
  • Added Web Store link to the bottom of New Tab page.
  • Experimental JavaScript Harmony (ECMAScript 6) support.[91]
  • Experimental Web Intents API.[92]
20.0.1132 2012-06-26 536.10 3.10.6.0
  • Experimental touch friendly Template:Dabbr adjustments. Context menus have extra vertical padding between items.[93]
  • New tab button is bigger and wider
21.0.1180 2012-07-31 537.1 3.11.10.6
  • Media Stream API (getUserMedia) enabled by default. (E.g. webcam access via JavaScript.)[94]
  • Gamepad API prototype available by default.
  • Added support for (pointer) and (hover) CSS media queries so sites can optimize their Template:Dabbr for touch when touch-screen support is available.
  • HTML5 audio/video and WebAudio now support 24-bit PCM wave files.
22.0.1229 2012-09-25 537.4 3.12.19.4
  • New-style packaged apps are enabled by default.
  • New menu icon, replacing the wrench icon.
  • Added support for TLS 1.1.[95][96]
  • Added support for color management ICC v2 profiles by default.[97]
23.0.1271 2012-11-06 537.10 3.13.7.1
  • Added Do Not Track preference[98]
  • Hardware video acceleration with 25% more efficient power consumption in some scenarios
  • Manager for site permission control
  • New icon for Chrome Web Store when opening new tab
  • PPAPI Flash Player (or Pepper-based Flash Player) replaced the NPAPI Flash Player on Mac also.[99]
24.0.1312 2012-10-30 537.17 3.14.5.0
25.0.1364 2012-12-19 537.22 3.15.11.5
  • Opus audio support
  • VP9 video support
  • External extension disabled by default[101]

Notes:

  • All versions support Windows. OS X 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).[102][103][104]
  • Old development and beta builds are not shown after they become stable releases.

Features

Google Chrome aims to be secure, fast, simple[105] and stable. There are extensive differences from its peers in Chrome's minimalistic user interface,[18] which is atypical of modern web browsers.[106] For example, Chrome does not render RSS feeds.[107] One of Chrome's strengths 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.[108][109] 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.[110] 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.[111] Both Internet Explorer 9 and Safari (version 6) have since merged the search and address bar.

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 has passed all aspects of the Acid3 test.[58]

Chrome has currently quite good support for JavaScript/ECMAScript according to Ecma International's ECMAScript standards conformance Test 262[112] (version ES5.1 of 2012-05-18). This test reports as final score the number of tests a browser failed; hence lower scores are better. In this test, Chrome version 23.0.1271 scored 9/11570, and the dev version 25.0.1364.5 scored 12/11572. For comparison, Firefox 15 scored 172/11750 and Internet Explorer 9 has a score of 600+, while Internet Explorer 10 has a score of 7.

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% covered) CSS 2.1 tests.[113]

On the HTML5 test (version 3.0), Chrome 23 on desktop scored 448 out of 500, with 13 bonus points. Chrome's tablet version was third place, with 390 points. Chrome got second place on mobile browsers, with 390 points.[114][115][116]

Security

See also: Browser 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".[18]

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.[117] 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";[118] 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.[18] 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.[119] On Linux sandboxing uses the seccomp mode.[120][121]

In December 2011 a report by Accuvant, funded by Google, rated the security (based on sandboxing) of Google Chrome as better than either Internet Explorer or Mozilla Firefox.[122]

Security vulnerabilities

See also: Comparison of web browsers § Security and vulnerabilities

No security vulnerabilities in Chrome had been successfully exploited in the three years of Pwn2Own from 2009–11.[123] However, Chrome was the first browser 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.[124][125][126]

Google's official response to the vulnerabilities was delivered by Jason Kersey, who congratulated the researchers, noting "We also believe that both submissions are works of art and deserve wider sharing and recognition."[127] The browser Version 23 addressed 15 security vulnerabilities in which six are rated as high sensitivity and fixed.[128]

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.[129] A May 2011 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. Referring to that study, Ars Technica wrote in July 2011 that "Even with the false positives, Microsoft's approach appears to be more secure."[130][131] A February 2012 study reported that Chrome 15 had a 34.1% malware-blocking rate.[132][133] Neither study analyzed exploits that install malware without the user being aware (for example clickjacking and drive-by downloads).

Google introduced new security functionality — download scanning protection — in Chrome 17.[84][134]

Plugins

  • Chrome supports plug-ins with the Netscape Plugin Application Programming Interface (NPAPI),[135] so that plug-ins (for example Adobe Flash Player) run as an unrestricted separate process outside the browser and cannot be sandboxed as tabs are. ActiveX is not supported.[135] On March 30, 2010 Google announced that the latest development version of Chrome would bundle Adobe Flash with 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.[136] Java applet support is available in Chrome with Java 6 update 12 and above.[137] Support for Java under Mac OS X was provided by a Java Update released on May 18, 2010.[138]
  • On August 12, 2009, Google introduced a replacement for NPAPI that is more portable and more secure[139] called Pepper Plugin API (PPAPI).[140] The default bundled PPAPI Flash Player (or Pepper-based Flash Player) was available on Chrome OS first, then replaced the NPAPI Flash Player on Linux from Chrome version 20, on Windows from version 21 (which also reduced Flash crashes by 20%),[141] and eventually came to Mac at version 23.[99]

Privacy

Privacy mode

The private browsing feature called Incognito mode prevents the browser from permanently storing any history information or cookies from the websites visited.[142] Incognito mode is similar to the private browsing feature in other web browsers. Chrome was the second browser to implement this feature, after Safari.

Usage tracking

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

Tracking methods
Method[144] Information sent When Optional? If optional, is default?
Installation Randomly generated token included in installer. Used to measure success rate of Google Chrome once at installation.[145]

On installation

No n/a
RLZ identifier[146] Encoded string, according to Google, contains non-identifying information how Chrome was downloaded and its install week, and is used to measure promotional campaigns.[145] Google provides the source code to decode this string.[53]
  • On Google search query
  • On first launch and first use of address bar[145]
 Partial[note 2][145] n/a
clientID[147] Unique identifier along with user preferences, logs of usage metrics and crashes. Un­known Yes[148] No
Omnibox predictions[147] Text typed into the address bar. While typing Yes Yes
Page not found Text typed into the address bar. Upon receiving "Server not found" response Yes Yes
Google Update (Windows) Information about how often Chrome is used, details about the OS and Chrome version. Un­known No n/a
Google Software Update (OS X)

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

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

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

Do Not Track

Main article: Criticism of Google § Do Not Track

In February 2012, Google announced that Chrome would support Do Not Track by the end of 2012 and the protocol was implemented on version 23.[152]

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

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.[153] 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.[154][155][156][157][158][159] 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.[160]

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.[161][162][163] 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.[164]

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

Chrome uses DNS prefetching to speed up website lookups,[169] as other browsers like Firefox,[170] Safari,[171] Internet Explorer (called DNS Pre-resolution),[172] and in Opera as a UserScript (not built-in).[173]

Chrome utilizes the faster SPDY protocol instead of HTTP[174][175] 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.[176]

Stability

A multi-process architecture is implemented in Chrome[177] where, by default, a separate process is allocated to each site instance and plugin. This procedure is termed process isolation,[178] 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,[179] 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.[18] This architecture is being adopted in upcoming versions of Safari[180] and Firefox.[181]

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.[18] Chrome Version 23 ensures its users a improved battery life for the systems supporting Chrome's GPU accelerated video decoding.[182][183]

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 Settings page to take the user to the new tab page or a custom home page.[184]

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

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

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

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

File:Chrome Logo.svg
Google Chrome logos. Top: 3D motif from project start until March 2011. Bottom: 2D motif from March 2011 to 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.[187] As of 2009, this function was unavailable on the Linux and Mac platforms.[188]

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

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

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.[189][190]

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

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

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.[191][192]

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

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

Extensions

Main article: Google Chrome Extensions

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

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

As of February 4, 2011, the extension gallery featured more than 11,500 extensions,[198] including official extensions from the Independent,[199] CEOP,[200] Transport for London,[201] Cricinfo,[202] Web of Trust (WOT)[203] and FIFA.[204]

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.[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 does not natively include the option to be the default browser, although on OSX it can be set through Safari's preferences. 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 auto-update 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 auto-update 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.

Color management

Main article: Color management

Chrome supports color management by using the system provided ICC v2 and v4 support on OS X, and from version 22 supports ICC v2 profiles by default on other platforms.[97]

Platforms

Chrome is available for[219]

  • Windows: XP Service Pack 2+ / Vista / 7 / 8
  • Mac OS X: 10.6 or later[220]
  • Linux: Ubuntu 8.04 or later / Debian 5 / OpenSuse 11.1 / Fedora

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]

  • iOS, iPhone, iPod touch, iPad
  • Android 4.0 or later

Android version

Main article: Google Chrome for Android

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

Notable features: synchronization with desktop Chrome to provide the same bookmarks and view the same browser tabs,[224] page pre-rendering,[225] hardware acceleration.[226]

Many of the latest HTML5 features: almost all of the Web Platform’s features: GPU-accelerated canvas, including CSS 3D Transforms, CSS animations, SVG, WebSocket (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.[225][227] Also supports mobile oriented features such as Device Orientation and Geolocation.[227]

Mobile customisations: swipe gesture tab switching,[224] link preview allows zooming in on (multiple) links to ensure the desired one is clicked,[224] font size boosting to ensure readability regardless of the zoom level.[227]

Missing in the mobile version are sandboxed tabs,[225][228] Safe Browsing,[225] apps or extensions,[226] Adobe Flash (now and in future),[226] WebGL, Native Client.[226]

Development changes: remote debugging,[225][229] part of the browser layer has been implemented in Java, communicating with the rest of the Chromium and WebKit code through Java Native Bindings.[227] 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.[227]

The April 17, 2012 update included the availability to access in 31 additional languages and in all countries where Google Play is available. A desktop version of a website can also be requested as opposed to a mobile version. In addition, Android users can now add bookmarks to their Android home screens if they choose and decide which apps should handle links opened in Chrome.[230]

On the June 27, 2012 Google Chrome for Android exited beta and became stable.[231]

Chrome 18.0.1026311, released at September 26, 2012 was the first version of Chrome for Android to support Intel x86 based mobile devices.[232]

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.[233] 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.[234][235][236][237][238]

Google announced Chrome OS on July 7, 2009.[239]

iOS version

Google Chrome for iOS is the mobile rendition of Google's Chrome web browser for Apple's iOS operating system as its name implies. It was released on the App Store on June 26, 2012. It supports the iPad, iPhone, and iPod touch, and requires that the device have at least iOS version 4.3 installed.[240] Per Apple's requirements for browsers released through the App Store, this version of Chrome uses the iOS WebKit, that is the mobile Safari iOS engine and components, but restricted from using their Nitro JavaScript engine.[241]

In a review by Chitika on July 18, 2012, Google Chrome was noted as having 1.5% of the iOS web browser market.[242]

Metro version

In June 2012, Google released the developers version of Chrome 21.[243] On Windows 8, this version of Chrome can be run in the Metro UI as long as it is set as the default browser on the computer. The Metro version of Chrome looks identical to its desktop counterpart and does not support the standard design principles of the Metro UI.

Usage

Usage share of web browsers according to StatCounter.[244]
The most used web browser by country in 2020[245]
Further information: Usage share of web browsers and Browser wars

In 2008, Matthew Moore in the The Daily Telegraph summarized 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."[246]

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".[247] 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."[248] 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.[249][250]

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[251]

Chrome overtook Firefox in November 2011. As of September 2012, according to StatCounter, Google Chrome had 34% worldwide usage share, making it the most widely used web browser, while Internet Explorer had 33% and Firefox had 22%.[10][252]

Along with Safari and Mozilla Firefox, Chrome receives a weekend "bump", which boosts its marketshare by as much as three percentage points on week-ends, at the expense of Internet Explorer.[253]

It was reported by StatCounter, a web analytics company, that for the single day of Sunday, March 18, 2012 Chrome was the most used web browser in the world for the first time. Chrome secured 32.7% of the global web browsing on that day, while Internet Explorer followed closely behind with 32.5%.[254]

From May 14–21, 2012 Google Chrome was responsible for more Internet traffic than Microsoft's Internet Explorer (for the first time), which long had held its spot as the most used web browser in the world.[255] According to StatCounter, 31.88% of web traffic was generated by Chrome for a sustained period of one week and 31.47% by Internet Explorer. Though Chrome has topped Internet Explorer for single day's usage in the past, this is the first time it has led for one full week.[256]

At the 2012 Google I/O developers' conference, Google claimed that there were 310 million active users of Chrome, almost double the number in 2011, which was stated as 160 million active users.[257]

See also

Notes

  1. ^ Google Chrome's WebKit layout engine and V8 JavaScript engine are all Free and open source software. Other parts may be open-source or proprietary. Google Chrome's Terms of Service makes the entire package proprietary freeware. (see Terms of Service text, section 9.2).
  2. ^ Browser must be downloaded directly from the Google Chrome website to opt-out of the RLZ identifier.

References

  1. ^ a b c d "Stable Channel Update for Desktop". October 29, 2024. Retrieved October 30, 2024.
  2. ^ "Stable Channel Desktop Update". September 13, 2023. Retrieved September 14, 2023.
  3. ^ a b "Chrome for Android Update". October 29, 2024. Retrieved October 30, 2024.
  4. ^ a b "Chrome Stable for iOS Update". October 29, 2024. Retrieved October 30, 2024.
  5. ^ "Stable Channel Desktop Update". September 13, 2023. Retrieved September 14, 2023.
  6. ^ "Chrome Beta for Desktop Update". October 30, 2024. Retrieved October 31, 2024.
  7. ^ "Chrome Beta for Android Update". October 30, 2024. Retrieved October 30, 2024.
  8. ^ "Chrome Beta for iOS Update". October 30, 2024. Retrieved October 31, 2024.
  9. ^ a b "Google Chrome Terms of Service". Google. Retrieved October 1, 2012.
  10. ^ a b "Top 5 Browsers from Apr to Sep 2012 - StatCounter Global Stats". StatCounter. Retrieved October 15, 2012.
  11. ^ Desktop Browser Market Share, Net Applications, retrieved September 25, 2012
  12. ^ Paul, Ryan (September 2, 2008). "Google unveils Chrome source code and Linux port". Ars Technica. Retrieved July 11, 2012.
  13. ^ "Google Chrome is built with open source code from Chromium." Retrieved from dev.chromium.org[dead link]
  14. ^ Julia Angwin (July 9, 2009). "Sun Valley: Schmidt Didn't Want to Build Chrome Initially, He Says". WSJ Digits Blog. Retrieved May 25, 2010.
  15. ^ Scott McCloud (September 1, 2008). "Surprise!". Google Blogoscoped. Retrieved September 1, 2008.
  16. ^ Philipp Lenssen (September 1, 2008). "Google Chrome, Google's Browser Project". Retrieved September 1, 2008.
  17. ^ Philipp Lenssen (September 1, 2008). "Google on Google Chrome – comic book". Google Blogoscoped. Retrieved September 1, 2008.
  18. ^ a b c d e f g h i j k l m n o "Google Chrome comic". Google Book Search. September 1, 2008. Retrieved September 2, 2008.
  19. ^ a b Pichai, Sundar (September 1, 2008). "A fresh take on the browser". Google Blog. Retrieved July 11, 2012. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  20. ^ "It was when not if... Google Chrome". 2008. Retrieved September 2, 2008. {{cite web}}: Unknown parameter |month= ignored (help)
  21. ^ "Be sure to read Chrome's fine print". CNET. Retrieved September 3, 2008.
  22. ^ Redirecting
  23. ^ "Google Chrome Terms of Service (English)". Retrieved September 4, 2008.
  24. ^ "Google Chrome update: First screenshot, and live-blog alert". CNet. September 1, 2008. Retrieved 2012‑07‑11. {{cite web}}: Check date values in: |accessdate= (help)
  25. ^ "Google launches Chrome web browser". The Canadian Press. Associated Press. September 2, 2008. Retrieved September 2, 2008.
  26. ^ "Come on Google... Chrome for Mac?". 2008. Retrieved November 22, 2008. {{cite web}}: Unknown parameter |month= ignored (help)
  27. ^ Gruener, Wolfgang (January 3, 2009). "Google Chrome crosses 1% market share again". Chicago (IL), USA: TG Daily. Retrieved July 11, 2012.
  28. ^ Shankland, Stephen (January 9, 2009). "Chrome gets Mac deadline, extensions foundation". CNET. Retrieved January 13, 2009.
  29. ^ "Early Access Release Channels". dev.chromium.org. Retrieved April 8, 2012.
  30. ^ "Danger: Mac and Linux builds available". Retrieved June 9, 2009.
  31. ^ Mark Larson (December 8, 2009). "Beta Update: Linux, Mac, and Windows". Google. Retrieved July 11, 2012.
  32. ^ a b "Google Chrome for the holidays: Mac, Linux and extensions in beta". Googleblog.blogspot.com. Retrieved July 11, 2012.
  33. ^ Brian Rakowski (May 25, 2010). "A new Chrome stable release: Welcome, Mac and Linux!". Google. Retrieved July 11, 2012.
  34. ^ "Microsoft offers browser choices to Europeans". BBC News. March 1, 2010. Retrieved July 11, 2012.
  35. ^ Peteris Krumins (September 5, 2008). "Code reuse in Google Chrome Browser". Retrieved May 13, 2010.
  36. ^ Wikimedia Traffic Analysis Report - Browsers, 2012-10, Wikimedia
  37. ^ Ian Fette (February 19, 2010). "Hello HTML5". Google. Retrieved July 11, 2012.
  38. ^ "HTML Video Codec Support in Chrome". blog.chromium.org. January 11, 2011. Retrieved April 8, 2012.
  39. ^ "Longer battery life and easier website permissions". chrome.blogspot.com. November 6, 2012. Retrieved December 3, 2012.
  40. ^ "Google Chrome Beta arrives on Android". Engadget. Retrieved 2012‑07‑11. {{cite news}}: Check date values in: |accessdate= (help)
  41. ^ "Chrome Out Of Beta, Default Browser Of Android 4.1". Muktware.com. June 28, 2012. Retrieved September 15, 2012.
  42. ^ Pachal, Peter (March 13, 2012). "Google Confirms It's Working on Chrome for Windows 8". Retrieved March 14, 2012.
  43. ^ "Change MSI from a wrapper to "full" MSI". Google. January 4, 2011. Retrieved April 8, 2012.
  44. ^ Paul, Ryan (2010). "Google offering MSI to simplify Chrome enterprise deployment". Ars Technica. Retrieved July 11, 2012. {{cite news}}: Unknown parameter |month= ignored (help)
  45. ^ "Google Update for Enterprise – Google Help". Google. Retrieved July 11, 2012.
  46. ^ "Issue 2423 – chromium – Windows Roaming Profile support – An open-source browser project to help move the web forward. – Google Project Hosting". Google. September 17, 2008. Retrieved April 8, 2012.
  47. ^ "Home (Chromium Developer Documentation)". Chromium Developer Documentation. dev.chromium.org. 2009. Retrieved May 5, 2009.
  48. ^ "Chromium Terms and Conditions". Google Code. September 2, 2008. Retrieved September 3, 2008.[dead link]
  49. ^ Chromium Project (2011). "ChromiumBrowserVsGoogleChrome". Retrieved July 10, 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  50. ^ 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.
  51. ^ "Google Chrome, Chromium, and Google". blog.chromium.org/. The Chromium Blog. 2008. Retrieved February 17, 2010.
  52. ^ "Differences between Google Chrome and Linux distro Chromium". Google. 2010. Retrieved September 1, 2010.
  53. ^ 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)
  54. ^ "Release Notes". The Chromium Projects.
  55. ^ "ChangeLog – v8". Google. Retrieved April 8, 2012.
  56. ^ "A fresh take on the browser". September 1, 2008. Retrieved July 11, 2012.
  57. ^ "Google Chrome Releases: Stable Update: Google Chrome 2.0.172.28".
  58. ^ a b Anthony Laforge. "Stable Channel Update". Google. Retrieved May 25, 2010.
  59. ^ "Google Chrome Releases: Stable Channel Update March 17, 2010". googlechromereleases.blogspot.com. March 17, 2010. Retrieved April 8, 2012.
  60. ^ Brian Rakowski (May 25, 2010). "Evolving from beta to stable with a faster version of Chrome". Google. Retrieved May 25, 2010.
  61. ^ "Adobe Flash Player support now enabled in Google Chrome's stable channel". June 30, 2010. Retrieved August 8, 2010.
  62. ^ "Bringing improved PDF support to Google Chrome". Chromium Blog. June 17, 2010. Retrieved October 24, 2010.
  63. ^ "Bringing another Chrome release to you, right on time". Google. Retrieved October 24, 2010.
  64. ^ "Stable, Beta Channel Updates". Google. Retrieved December 3, 2010.
  65. ^ "Safer plug-ins, faster search, and richer graphics". Google. Retrieved December 17, 2010.
  66. ^ "WebP Home". Google. Retrieved February 3, 2011.
  67. ^ "Dev Channel Update". Google. Retrieved January 21, 2011.
  68. ^ "Issue 48607: Sandbox GPU process". Retrieved March 21, 2012.
  69. ^ "A New Crankshaft for V8". Google. Retrieved December 17, 2010.
  70. ^ "Chrome Releases: Chrome Stable Release". googlechromereleases.blogspot.com. March 8, 2011. Retrieved April 8, 2012.
  71. ^ "Chrome Beta Release". March 22, 2011. Retrieved March 23, 2011.
  72. ^ a b Rura, Steve (2011). "A fresh take on an icon". Retrieved March 22, 2011. {{cite web}}: Unknown parameter |month= ignored (help)
  73. ^ a b "Chrome Stable Release". June 7, 2011. Retrieved June 7, 2011.
  74. ^ "Google Operating System: Chrome shifts into a new gear" (Document). Google Operating System (Unofficial Google Blog). June 7, 2011Template:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link)
  75. ^ Bentzel, Chris (June 16, 2011). "Google Chrome Blog: Faster than fast". chrome.blogspot.com. Retrieved August 21, 2011.
  76. ^ "Building better web apps with a new Chrome Beta". Retrieved August 15, 2011.
  77. ^ Adam Langley (August 16, 2010). "DNSSEC authenticated HTTPS in Chrome". ImperialViolet. Retrieved April 8, 2012.
  78. ^ "Chrome Beta Channel Update". Retrieved August 15, 2011.
  79. ^ a b c "Download Google Chrome 15.0.874.15 Dev with Fixes for the Revamped New Tab Page". Retrieved September 19, 2011.
  80. ^ a b "Download Google Chrome 16 Dev and Chrome 15 Beta". Retrieved September 23, 2011.
  81. ^ "Issue 50811 – chromium – Switch Chromium to ffmpeg native vp8 decoder – An open-source browser project to help move the web forward. – Google Project Hosting". Google. July 30, 2010. Retrieved April 8, 2012.
  82. ^ "Chromium Issue 48119: Feature request: optional permissions in Chrome extensions" (Document). Google Code. July 1, 2010Template:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link)
  83. ^ "Chromium Issue 99332: Remove sidetabs" (Document). Google Code. October 6, 2011Template:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link)
  84. ^ a b c d "Stable Channel Update". Retrieved February 9, 2012.
  85. ^ "Google Chrome 17 FINAL". Retrieved February 9, 2012.[dead link]
  86. ^ "Chromium Issue 15548: Search Engines should be synced". Google. June 28, 2009. Retrieved April 8, 2012.
  87. ^ Ionut Ilascu (January 19, 2012). "Google Chrome Beta 17.0.963.38 Disables GAIA Photo". Softpedia. Retrieved December 27, 2012.
  88. ^ a b "Faster graphics for older PCs in Chrome 18".
  89. ^ "[chrome] Revision 119099". Src.chromium.org. Retrieved May 23, 2012.
  90. ^ "Google Chrome Blog: All your tabs, accessible everywhere". chrome.blogspot.com.au. April 10, 2012. Retrieved May 23, 2012.
  91. ^ "Google Chrome 19 Adds Support for Next-Generation JavaScript". Softpedia. February 11, 2012. Retrieved May 15, 2012.
  92. ^ "Connect with Web Intents". Google. May 16, 2012. Retrieved May 16, 2012.
  93. ^ "[chrome] Revision 133210]".
  94. ^ "Decreased input padding, 8-bit canvas and getUserMedia() « Peter Beverloo". Peter Beverloo. Retrieved May 23, 2012.
  95. ^ Google (May 29, 2012). "Dev Channel Update". Retrieved June 1, 2011. {{cite web}}: |author= has generic name (help)
  96. ^ Google (August 21, 2012). "Stable Channel Update". Retrieved August 22, 2012. {{cite web}}: |author= has generic name (help)
  97. ^ a b Issue 143: Handle color profiles in tagged images
  98. ^ Bright, Peter (September 14, 2012). "Do Not Track support added to Chrome, arriving by the end of the year". Ars Technica. Retrieved November 2, 2012.
  99. ^ a b "Securing Flash Player for our Mac users". Google. Retrieved November 14, 2012.
  100. ^ a b c "A web developer's guide to the latest Chrome Beta". November 8, 2012. Retrieved November 9, 2012.
  101. ^ "No more silent extension installs". Chromium Blog. December 24, 2012. Retrieved December 24, 2012.
  102. ^ Sundar Pichai. "Google Chrome Blog: Introducing Chrome for Android". chrome.blogspot.com. Retrieved February 9, 2012Template:Inconsistent citations{{cite web}}: CS1 maint: postscript (link)
  103. ^ "The Chromium Blog: A deeper look at Chrome for Android". blog.chromium.org. Retrieved February 9, 2012Template:Inconsistent citations{{cite web}}: CS1 maint: postscript (link)
  104. ^ "Chrome for Android Beta". market.android.com. Retrieved February 9, 2012Template:Inconsistent citations{{cite web}}: CS1 maint: postscript (link)
  105. ^ "Technology overview – Google Chrome".
  106. ^ Gloson (December 4, 2008). "Google Chrome's Unique Features". Retrieved May 13, 2010.
  107. ^ "Issue 84 – chromium – RSS or Atom support needed – An open-source browser project to help move the web forward. – Google Project Hosting". Google. September 2, 2008. Retrieved April 8, 2012.
  108. ^ Stephen Shankland (September 2, 2008). "Speed test: Google Chrome beats Firefox, IE, Safari – Business Tech". CNET News. Retrieved May 13, 2010.
  109. ^ Kevin Purdy (June 11, 2009). "Lifehacker Speed Tests: Safari 4, Chrome 2, and More – Browsers". Lifehacker. Retrieved May 13, 2010.
  110. ^ "12 Unique features of Chrome". TechStroke. September 3, 2008. Retrieved April 8, 2012.
  111. ^ Rafe Needleman (May 14, 2008). "The future of the Firefox address bar". CNET News. Retrieved May 13, 2010.
  112. ^ "ECMAScript test262". ECMAScript. Retrieved May 6, 2011.
  113. ^ "CSS 2.1 Test Suite RC6 Results". W3C. Retrieved May 6, 2011.
  114. ^ "HTML5 test". Sights. Retrieved October 7, 2012.
  115. ^ "HTML5 test". Sights. Retrieved October 7, 2012.
  116. ^ "HTML5 test". Sights. Retrieved October 7, 2012.
  117. ^ Chung, Marc (September 5, 2008). "chromes-process model explained". Retrieved September 10, 2008.
  118. ^ Google (September 1, 2008). "Google Chrome". Retrieved September 3, 2008. {{cite web}}: |author= has generic name (help)[dead link]
  119. ^ 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)
  120. ^ 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)
  121. ^ Jake Edge (August 19, 2009). "Google's Chromium sandbox". Retrieved February 17, 2011.
  122. ^ Goodin, Dan (December 9, 2011). "Chrome is the most secured browser - new study". The Register. Retrieved October 15, 2012.
  123. ^ Gregg Keizer, Google's Chrome untouched at Pwn2Own hack match, Computerworld, March 10, 2011
  124. ^ "Pwn2Own 2012: Google Chrome browser sandbox first to fall". www.zdnet.com. March 7, 2012. Retrieved April 8, 2012.
  125. ^ "CanSecWest Pwnium: Google Chrome hacked with sandbox bypass". www.zdnet.com. March 7, 2012. Retrieved April 8, 2012.
  126. ^ "Teenager hacks Google Chrome with three 0day vulnerabilities". www.zdnet.com. March 9, 2012. Retrieved April 8, 2012.
  127. ^ Kersey, Jason (March 10, 2012). "Chrome Stable Update". Retrieved March 10, 2012.
  128. ^ "Chrome 23 Closes 15 Security Vulnerabilities, Promises Longer Battery Life & Added Do Not Track (DNT)". Retrieved November 9, 2012.
  129. ^ Hughes, Brian. "Virus Bulletin : 2010 – Social engineering trumps a zero-day every time". AVG Technologies. Retrieved July 21, 2011.
  130. ^ Bright, Peter (July 16, 2011). "Internet Explorer 9 utterly dominates malware-blocking stats". Ars Technica. Retrieved July 16, 2011.
  131. ^ "Web Browser Group Test Socially-Engineered Malware". NSS Labs. July 16, 2011.
  132. ^ Samson, Ted (February 7, 2012). "Update: Internet Explorer aces security test as Google faces accusations". InfoWorld. Retrieved June 15, 2012.
  133. ^ Arghire, Ionut (2012‑02‑07). "IE9 Still Most Effective at Blocking Social-Engineered Malware, NSS Labs Finds". Softpedia. Retrieved 2012‑06‑15. {{cite web}}: Check date values in: |accessdate= and |date= (help)
  134. ^ Paul, Ryan (2012-02-09). "Chrome 17 released, will preload autocompleted URLs as you type". Ars Technica. Retrieved 2012‑06‑15. {{cite web}}: Check date values in: |accessdate= (help)
  135. ^ a b "Google Chrome FAQ for web developers". Google. Retrieved April 8, 2012.
  136. ^ 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)
  137. ^ "Java and Google Chrome". java.com. Retrieved December 11, 2009.
  138. ^ "Issue 10812 – chromium – No java plugin support yet". Google. Retrieved May 18, 2010.
  139. ^ Pepper.wiki
  140. ^ Pepper Plugin API (PPAPI)
  141. ^ "Chromium Blog: The road to safer, more stable, and flashier Flash". blog.chromium.org. August 8, 2012. Retrieved August 29, 2012.
  142. ^ "Explore Google Chrome Features: Incognito Mode". September 2, 2008. Retrieved September 4, 2008.
  143. ^ "Chromium Blog: Google Chrome, Chromium, and Google". blog.chromium.org. October 1, 2008. Retrieved April 8, 2012.
  144. ^ a b "SRWare Iron webpage". Retrieved October 12, 2008.
  145. ^ a b c d "Google Chrome Privacy Whitepaper" (PDF). Retrieved April 8, 2012.
  146. ^ "&rlz= in Google referrer: Organic traffic or AdWords?". Retrieved February 27, 2009.
  147. ^ a b c "Google Reacts to Some Chrome Privacy Concerns". Retrieved September 24, 2008.
  148. ^ Controlled by the setting "Send usage statistics and error reports". Default off.
  149. ^ "Google Chrome Privacy Notice" (Document). Google. December 13, 2011Template:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link)
  150. ^ "Google Chrome Unique Identifier Change". March 16, 2010. Retrieved March 24, 2010.
  151. ^ Fried, Ina (September 3, 2008). "Google's Omnibox could be Pandora's box". Retrieved May 13, 2010.
  152. ^ "Google and Chrome To Support Do Not Track". Retrieved March 3, 2012.
  153. ^ "V8 Benchmark suite". Google code. Retrieved September 3, 2008.[dead link]
  154. ^ Rupert Goodwins (September 2, 2008). "Google Chrome – first benchmarks. Summary: wow".[dead link]
  155. ^ "Google Chrome Javascript Benchmarks". jrm.cc. September 1, 2008. Retrieved April 8, 2012.
  156. ^ Adrian Kingsley-Hughes (September 2, 2008). "Google Chrome is insanely fast ... faster than Firefox 3.0".
  157. ^ Stephen Shankland (September 2, 2008). "Speed test: Google Chrome". CNET Business Tech.
  158. ^ Alexander Limi (September 2, 2008). "Chrome: Benchmarks and more". Retrieved May 13, 2010.
  159. ^ 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.
  160. ^ Scott M. Fulton, III (October 11, 2010). "Firefox in the dust: Opera poised to reclaim browser performance lead". Retrieved November 6, 2010.[dead link]
  161. ^ Stephen Shankland (September 3, 2008). "Firefox counters Google's browser speed test – Business Tech". CNET News. Retrieved May 13, 2010.
  162. ^ Eich, Brendan (September 3, 2008). "TraceMonkey Update".[dead link]
  163. ^ Stephen Shankland (November 3, 2008). "Third Chrome beta another notch faster – News". Builder AU. Retrieved May 13, 2010.
  164. ^ Resig, John (September 3, 2008). "JavaScript Performance Rundown".
  165. ^ Maciej Stachowiak (September 18, 2008). "WebKit blog: Introducing SquirrelFish Extreme". Retrieved May 13, 2010.
  166. ^ Cameron Zwarich (September 18, 2008). "SquirrelFish Extreme has landed!". Retrieved May 13, 2010.[dead link]
  167. ^ Stephen Shankland (September 22, 2008). "Step aside, Chrome, for Squirrelfish Extreme – News". Builder AU. Retrieved May 13, 2010.
  168. ^ Charles Ying (September 19, 2008). "SquirrelFish Extreme: Fastest JavaScript Engine Yet". Retrieved May 13, 2010.
  169. ^ a b Preston Gralla (September 3, 2008). "Three hidden Chrome features you'll love". Retrieved September 16, 2008.
  170. ^ "DNS prefetching for Firefox". November 8, 2008.
  171. ^ Apple Inc. (June 7, 2010). "What's new in Safari 5". Retrieved July 6, 2010.
  172. ^ "Internet Explorer 9 Network Performance Improvements". Blogs.msdn.com. March 17, 2011. Retrieved April 8, 2012.
  173. ^ João Eiras. "Page prefetcher". userjs.org. Retrieved April 8, 2012.
  174. ^ "chrome] Index of /trunk/src/net/spdy – Chromium SPDY client implementation". src.chromium.org. Retrieved April 8, 2012.
  175. ^ "SPDY Proxy Examples – The Chromium Projects". www.chromium.org. Retrieved April 8, 2012.
  176. ^ "SPDY on Google servers? – spdy-dev | Google Groups". Google. Retrieved April 8, 2012.
  177. ^ Reisn, Charlie (September 11, 2008). "Multi-process Architecture". Retrieved September 12, 2008.
  178. ^ "Process Models". The Chromium Projects. Google. September 3, 2008. Retrieved September 12, 2008.
  179. ^ Prince, Brian (December 11, 2008). "Google Chrome Puts Security in a Sandbox". eWeek.com. Ziff Davis Enterprise Holdings Inc. Retrieved June 4, 2010.
  180. ^ "[webkit-dev] Announcing WebKit2". lists.webkit.org. Retrieved April 8, 2012.
  181. ^ "Firefox Lorentz beta available for download and testing". Mozilla. April 8, 2010.
  182. ^ "Chrome 23 Closes 15 Security Vulnerabilities, Promises Longer Battery Life & Added Do Not Track (DNT)". Retrieved November 9, 2012.
  183. ^ "Longer battery life and easier website permissions". Retrieved November 6, 2012.
  184. ^ Google (2012). "Set your home page". Retrieved May 22, 2012. {{cite web}}: |last= has generic name (help)
  185. ^ "A Speedier Google Chrome for all users". Google Chrome Blog.
  186. ^ Anthony Laforge (September 15, 2009). "Google Chrome after a year: Sporting a new stable release". Google. Retrieved May 13, 2010.
  187. ^ Kevin Purdy (September 2, 2009). "Add a Bookmark Button to Google Chrome's Toolbar". Lifehacker. Retrieved May 13, 2010.
  188. ^ 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)
  189. ^ "Chromium url_constants.cc". Retrieved September 1, 2010.
  190. ^ 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)
  191. ^ "Chrome Web Store". Google. May 19, 2010. Retrieved May 24, 2010.
  192. ^ Erik Lay (May 19, 2010). "The Chrome Web Store". Google. Retrieved May 24, 2010.
  193. ^ 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)
  194. ^ 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)
  195. ^ Aaron Boodman (September 9, 2009). "Extensions Status: On the Runway, Getting Ready for Take-Off". Google. Retrieved May 13, 2010.
  196. ^ Erik Kay (December 8, 2009). "Extensions beta launched, with over 300 extensions!". Google. Retrieved May 13, 2010.
  197. ^ Nick Baum (January 25, 2010). "Over 1,500 new features for Google Chrome". Google Chrome Blog. Retrieved May 13, 2010.
  198. ^ "Security improvements and registration updates for the Google Chrome Extensions Gallery". August 19, 2010.
  199. ^ "Official Independent Chrome Extension".
  200. ^ "CEOP Official Chrome Extension".
  201. ^ "Official TfL Chrome Extension".
  202. ^ from www.espncricinfo.com. "Chrome Web Store – ESPN Cricinfo". Google. Retrieved April 8, 2012.
  203. ^ "WOT – Google Chrome extension gallery".
  204. ^ "Official World Cup FIFA Chrome Extension".
  205. ^ "Chrome Web Store Help". Google. Retrieved April 8, 2012.
  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. ^ "Chrome Web Store". Google. Retrieved April 8, 2012.
  208. ^ Basic settings: Change browser theme Google Chrome Help
  209. ^ "Google — 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, 2012Template:Inconsistent citations{{cite web}}: CS1 maint: postscript (link).
  215. ^ David Dorwin (May 14, 2009). "Google Update Releases Update Controls". Retrieved May 13, 2010.
  216. ^ "Google Chrome voor Windows – Overeenkomst voor de Algemene voorwaarden". Google. April 28, 2011. Retrieved April 8, 2012.
  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. ^ Google. "System requirements : Install or update Google Chrome : Google Chrome Help". Retrieved April 8, 2011. {{cite web}}: |author= has generic name (help)
  220. ^ "Chrome no longer supports Mac OS X 10.5". Google Chrome support page. Retrieved August 6, 2012.
  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. ^ "Install Chrome for Android Beta – Google Chrome Help". Google. Retrieved April 6, 2012.
  224. ^ a b c "Beta version of Chrome for Android 4.0 released". www.neowin.net. Retrieved February 9, 2012Template:Inconsistent citations{{cite web}}: CS1 maint: postscript (link).
  225. ^ a b c d e "Google Operating System: Chrome for Android". googlesystem.blogspot.com. February 27, 2004. Retrieved February 9, 2012Template:Inconsistent citations{{cite web}}: CS1 maint: postscript (link).
  226. ^ a b c d "Google Chrome for Android – 23 Questions and Answers" (Document). Chrome StoryTemplate:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link)
  227. ^ a b c d e "Bringing Google Chrome to Android" (Document). Peter Beverloo. January 30, 2012Template:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link).
  228. ^ "Security overview" (Document). GoogleTemplate:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link).
  229. ^ "Google Chrome for Android: Remote Debugging" (Document). GoogleTemplate:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link).
  230. ^ Lardinois, Frederic (April 17, 2012), Chrome For Android Gets Desktop View, Home Screen Bookmarks, File Downloads
  231. ^ "Google Chrome for Android comes out of beta, Hits Play today" (Document). Engadget. June 27, 2012Template:Inconsistent citations {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)CS1 maint: postscript (link).
  232. ^ Chrome for Android Update
  233. ^ 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.
  234. ^ Sengupta, Caesar (November 19, 2009). "Releasing the Chromium OS open source project". Official Google Blog. Google, Inc. Retrieved November 19, 2009.
  235. ^ Stokes, Jon (January 19, 2010). "Google talks Chrome OS, HTML5, and the future of software". Ars Technica. Retrieved January 23, 2010.
  236. ^ Womack, Brian (July 8, 2009). "Google to Challenge Microsoft With Operating System". Bloomberg. Retrieved July 8, 2009.
  237. ^ Hansell, Saul (July 8, 2009). "Would you miss Windows with a Google operating system?". New York Times. Retrieved July 8, 2009.
  238. ^ Pichai, Sundar (July 7, 2009). "Introducing the Google Chrome OS". Official Google Blog. Google, Inc. Retrieved July 16, 2009.
  239. ^ Mediati, Nick (July 7, 2009). "Google Announces Chrome OS". PC World. Retrieved July 8, 2009.
  240. ^ Apple's App Store Chrome entry.
  241. ^ Forbes Google Chrome on iOS Hits #1 Free App
  242. ^ Reisinger, Don. "Chrome already nabs 1.5 percent of iOS browser market". CNET. Retrieved July 18, 2012.
  243. ^ Newman, Jared. "Google Chrome Gets Early Metro-Style App for Windows 8". PCWorld. Retrieved June 13, 2012.
  244. ^ "Top 5 Browsers from December 2010 to December 2011". StatCounter. Retrieved January 8, 2012.
  245. ^ "Browser Market Share Worldwide - September 2019". Statcounter. September 2019. Retrieved October 19, 2019.
  246. ^ Moore, Matthew (September 2, 2008). "Google Chrome browser: Review of reviews". Daily Telegraph. Retrieved September 24, 2011.
  247. ^ 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)
  248. ^ 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)[dead link].
  249. ^ "Thoughts on Chrome & More". John's Blog. September 1, 2008. Retrieved May 13, 2010.
  250. ^ Collins, Barry (September 2, 2008). "Mozilla: Google's not trying to kill us" (Document). PC Pro. {{cite document}}: Unknown parameter |accessdate= ignored (help); Unknown parameter |url= ignored (help)
  251. ^ Mediati, Nick (September 3, 2008). "Google Chrome Web Browser". PC World. Retrieved September 7, 2008. {{cite web}}: Check date values in: |date= (help)
  252. ^ For additional sources see Usage share of web browsers#Summary table
  253. ^ "Global Web Browser Marketshares". Clicky Analytics. Retrieved April 8, 2012.
  254. ^ Chrome is world's number one browser for a day, StatCounter Global Stats press release, March 21, 2012
  255. ^ "Chrome overtakes Internet Explorer as No. 1 browser -- maybe". CNN. Retrieved May 21, 2012.
  256. ^ Pachal, Peter. May 21, 2012. Google Chrome Now the No. 1 Browser in the World, mashable.com.
  257. ^ "Chrome tops 310 million users, almost 100% growth over last year". June 28, 2012.
Wikimedia Commons has media related to Google Chrome.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Google_Chrome&oldid=531920795"