Google Chrome – Wikipedia – ABOUT MAG 2020

Web browser developed by Google

Google Chrome
Google Chrome icon (September 2014) .svg
Google Chrome on Windows 10 screenshot.png
Developer (s) Google LLC
initial release September 2, 2008; 11 years ago (9/2/2008)
Stable release (s) [±]
Windows, macOS, Linux 81.0.4044.92 / April 7, 2020; 6 days ago (2020-04-07)[1]
Android 81.0.4044.96 / April 7, 2020; 6 days ago (2020-04-07)[2]
iOS 81.0.4044.62 / April 7, 2020; 6 days ago (2020-04-07)[3]
View versions [±]
Beta (Windows, macOS, Linux) 81.0.4044.92 / April 2, 2020; 11 days ago (2020-04-02)[4]
Beta (Android) 81.0.4044.96 / April 6, 2020; 7 days ago (2020-04-06)[5]
Beta (iOS) 83.0.4103.7 / April 9, 2020; 2 days ago (2020-04-09)[6]
Dev (Windows, macOS, Linux) 83.0.4103.7 / April 8, 2020; 3 days ago (2020-04-08)[7]
Dev (Android) 83.0.4103.7 / April 8, 2020; 3 days ago (2020-04-08)[6]
Dev (iOS) 84.0.4106.0 / April 7, 2020; 6 days ago (2020-04-07)[6]
Canary (Windows, macOS) 84.0.4113.0 / April 13, 2020; 2 days ago (2020-04-13)[6]
Canary (Android) 84.0.4113.0 / April 13, 2020; 2 days ago (2020-04-13)[6]
Written in Ç, C ++, Java (Android app only), Javascript, Python[8][9][10]
Engines Blink (WebKit on iOS), V8
Operational system
Platform IA-32, x86-64, ARMv7, ARMv8-A
Included with
Available in 47 languages[13]
Type Web browser, mobile browser
License Owner freeware, based on open source components.[14][note 1]
Internet network location www.Google.with/ chrome/

Google Chrome it is a multiplataform web browser Developed by Google. It was first launched in 2008 to Microsoft Windowsand it was later ported for Linux, Mac OS, iOSand Android. The browser is also the main component of the Chrome OS, where it serves as a platform for web applications.

Most Chrome source code comes from Google open code Chromium project, but Chrome is licensed as the owner freeware.[14] WebKit was the original rendering engine, but Google eventually forked to create the Blink motor; all Chrome variants, except iOS, now use Blink.[15]

In April 2020, StatCounter estimates that Chrome has a 68% worldwide browser market share (after reaching 72.36%) on traditional PCs and 64% on all platforms.[16][17] Because of this success, Google has expanded the “Chrome” brand to other products: Chrome OS, Chromecast, Chromebook, Chromebit, Chromeboxand Chromebase.


Google CEO Eric Schmidt opposed the development of an independent browser for six years. He stated that “at the time Google was a small company” and did not want to experience “bruises browser wars“. After the co-founders Sergey Brin and Larry Page hired several Mozilla Firefox developers and built a Chrome demo, Schmidt said that “it was so good it forced me to change my mind”.[18]

In September 2004, rumors emerged that Google built a web browser. Online magazines and U.S. newspapers stated at the time that Google was hiring former Microsoft web developers, among others. It also came shortly after the final release of Mozilla Firefox 1.0, which was growing in popularity and gaining market share from Internet Explorer, who suffered from major security problems.[19] The development of the browser was led by Sundar Pichai.[20]


The launch announcement was originally scheduled for September 3, 2008 and a comic book by Scott McCloud it should be sent to journalists and bloggers explaining the features of the new browser.[21] Copies destined for Europe were sent in advance and German blogger Philipp Lenssen of Google Blogoscoped made a digitized copy of the 38-page comic book available on its website after receiving it on September 1, 2008.[22][23] Google subsequently made the comics available in Google Books,[24] and mentioned it on his official blog, along with an explanation for the early release.[25] The product was named “Chrome” as an initial development project code name, because it is associated with fast cars and speed. Google kept the name of the development project as the name of the final release, as a “sassy” or ironic nickname, as one of the main goals was to minimize the chrome user interface.[26][27]

Public release

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

The browser was launched publicly for the first time on September 2, 2008 to Windows XP and later, with 43 languages ​​supported, officially beta version,[28] and as a stable public release on December 11, 2008. On the same day, a CNET The news drew attention to a passage in the Terms of Service statement for the initial beta version, which appeared to grant Google a license for all content downloaded by the Chrome browser.[29] This ticket was inherited from Google’s general terms of service.[30] Google immediately responded to these criticisms by stating that the language used was borrowed from other products and removed that passage from the Terms of Service.[14]

Chrome quickly gained about 1% usage share.[25][31][32] After the initial increase, usage share fell to a low of 0.69% in October 2008. Then it started to rise again, and in December 2008, Chrome again passed the 1% limit.[33] In early January 2009, CNET reported that Google planned to release versions of Chrome for OS X and Linux in the first half of the year.[34] The first official developer previews of Chrome OS X and Linux were announced on June 4, 2009,[35] with a blog post saying many features were missing and intended for early comment, rather than general use.[36] In December 2009, Google released beta versions of Chrome for OS X and Linux.[37][38] Google Chrome 5.0, announced on May 25, 2010, was the first stable release to support all three platforms.[39]

Chrome was one of the twelve browsers offered on the for European Economic Area Microsoft Windows users in 2010.[40]


Chrome was built from 25 different code libraries from Google and third parties, such as MozillaIt’s Portable Netscape runtime, Network security services, NPAPI (discarded in version 45),[41] Skia Graphics Engine, SQLite, and several other open source projects.[42] The V8 Javascript virtual machine was considered a project important enough to be divided (as it was Adobe/MozillaIt’s Tamarin) and managed by a separate team in Denmark, coordinated by Lars Bak at the Aarhus. According to Google, existing implementations were designed “for small programs, where system performance and interactivity were not that important”, but Web applications such as Gmail “are using the web browser to the fullest when it comes to SUN manipulations and Javascript“and therefore would benefit significantly from a JavaScript engine that could work faster.

Chrome initially used WebKit’s rendering engine to display web pages. In 2013, they forked the WebCore component to create your own layout engine Blink. Based on WebKit, Blink uses only the “WebCore” components of WebKit, while replacing other components, such as its own multi-process architecture, in place of the native implementation of WebKit.[15] Chrome is tested internally with unit test, automated scripting of user actions, fuzz test, as well as WebKit layout tests (99% of which Chrome is said to have passed) and against sites commonly accessed within the Google index in 20 to 30 minutes.[24] Google created Gears for Chrome, which added features for web developers typically related to building web applications, including offline support.[24] Google disabled Gears when the same functionality became available on HTML5 standards.[43]

On January 11, 2011, Chrome product manager Mike Jazayeri announced that Chrome would remove H.264 video codec support for the HTML5 player, citing the desire to align Google Chrome with the open codecs currently available in the Chromium project, on which Chrome is based.[44] Despite this, on November 6, 2012, Google released a version of Chrome on Windows that added hardware accelerated H.264 video decoding.[45] In October 2013, Cisco announced that it was supplying its open source H.264 codecs and would cover all required fees.[46]

On February 7, 2012, Google launched Google Chrome Beta for Android 4.0 devices.[47] On many new devices with Android 4.1 and later pre-installed, Chrome is the default browser.[48] In May 2017, Google announced a version of Chrome for augmented reality and virtual reality devices.[49]

Version history


Google Chrome has a minimalist user interface, with its user interface principles later implemented in other browsers. For example, the merger of Address bar and search bar on omnibox.[50] Chrome also has a reputation for strong browser performance.[51][52]

Synchronization of bookmarks and settings

Chrome allows users to sync their bookmarks, history and settings across all devices with the installed browser by sending and receiving data through a chosen Google Account, which in turn updates all Chrome login instances. This can be authenticated using Google credentials or a sync password.

Web standards support

The results of the Acid3 test on Google Chrome 4.0

The first version of Google Chrome passed both Acid1 and Acid2 tests. As of version 4.0, Chrome has gone through all aspects of Acid3 test.[53]

In May 2011, Chrome has very good support for JavaScript /ECMAScript according Ecma International262 ECMAScript compliance test[54] (version ES5.1, May 18, 2012). This test reports as the final score the number of tests that a browser has failed; therefore, lower scores are better. In this test, Chrome version 37 got 10 failures / 11,578 approved. For comparison, Firefox 19 had 193 flaws / 11,752 passed and Internet Explorer 9 has more than 600 flaws, while Internet Explorer 10 has 7 flaws.

In 2011, in the official CSS 2.1 testing suite of the standardization organization W3C, WebKit, Chrome’s rendering engine, passes 89.75% (89.38% of the 99.59% covered) in CSS 2.1 tests.[55]

In testing HTML5 web standards, Chrome 41 scores 518 out of 555 points, placing it ahead of the five most popular desktop browsers.[56][57] Chrome 41 on Android gets 510 out of 555 points.[58][59][60] Chrome 44 has 526 points, just 29 points less than the maximum score.[61]


Chrome periodically retrieves updates from two blacklists (one to phishing and one for malware) and warns users when they try to visit a site flagged as potentially harmful. This service is also available for use by third parties through a free public service. API called “Google Safe Browsing API “.[24]

Chrome uses a process allocation model to sandbox separators.[62] Using the least privilege principle, each guiding process cannot interact with critical memory functions (for example, OS memory, user files) or other guiding processes – similar to Microsoft’s “Protected Mode” used by Internet Explorer 9 or better. The The Sandbox Team It is said that “it took this limit of the existing process and turned it into a jail“. This imposes a computer security model whereby there are two levels of multilevel security (of the user and sandbox) it’s the sandbox can only respond to communication requests initiated by the of the user.[63] On Linux, sandboxing uses the seccomp mode.[64][65]

In January 2015, TorrentFreak reported that using Chrome when connected to the Internet using a VPN can be a serious security issue due to browser support for WebRTC.[66]

On September 9, 2016, it was reported that, starting with Chrome 56, users will be warned when they visit unsafe HTTP sites to encourage more sites to transition to HTTPS.[67]

On December 4, 2018, Google announced the launch of Chrome 71 with new security features, including an internal ad system. In addition, Google has also announced its plan to crack down on sites that make people unwittingly sign up for mobile subscription plans.[68]

Password management


Since 2008, Chrome has been criticized for not including a master password to prevent casual access to a user’s passwords. Chrome developers have indicated that a master password does not provide real security against determined hackers and have refused to implement one. The errors recorded in this problem were marked as “WontFix”.[69][70] In February 2014, Google Chrome prompts the user to enter the Windows account password before showing the saved passwords.[71]


In Linux, Google Chrome / Chromium can store passwords in three ways:

Google Chrome / Chromium chooses which store to use automatically, based on desktop environment in use.[72]

Passwords stored in GNOME Keychain or KWallet are encrypted on the disk and access to them is controlled by a dedicated daemon software. Passwords stored in plain text are not encrypted. For this reason, when GNOME Keyring or KWallet is in use, all unencrypted passwords that were previously stored will be automatically moved to encrypted storage.

Support for using GNOME Keyring and KWallet was added in version 6, but their use (when available) was not done in standard mode until version 12.

Although Google Chrome / Chromium chooses which store to use automatically, the store to use can also be specified with a command line argument:

  • –password-store = gnome (to use GNOME Keyring)
  • –password-store = kwallet (to use KWallet)
  • –password-store = basic (to use plain text storage)
Mac OS

As of version 45, the Google Chrome password manager is no longer integrated with Locksmith, since interoperability goal is no longer possible.[73]

Security vulnerabilities

No security vulnerabilities in Chrome have been exploited in the three years since Pwn2Own from 2009 to 2011.[74]

At Pwn2Own 2012, Chrome was defeated by a French team that used zero-day explorations in the version of Flash shipped with Chrome to take complete control of a fully corrected version 64-bit Windows 7 PC using a blocked website that overcame the Chrome sandbox.[75]

Chrome was compromised twice in CanSecWest 2012 Pwnium.[75][76][77] The official response from Google to the explorations was given by Jason Kersey, who congratulated the researchers, noting “We also believe that the two submissions are works of art and deserve greater sharing and recognition”.[78] Fixes for these vulnerabilities were deployed within 10 hours of submission.[79][80]

A significant number of security vulnerabilities in Chrome occur in the Adobe Flash Player. For example, the successful Pwn2Own attack on Chrome in 2016 featured four security vulnerabilities. Two of the vulnerabilities were in Flash, one in Chrome and one in the Windows kernel.[81] In 2016, Google announced that it planned to eliminate Flash Player in Chrome starting with version 53. The first phase of the plan is to disable Flash for ads and “background analysis”, with the ultimate goal of disabling it completely by the end of the year, except on specific sites that Google considered broken without it. Flash would be reactivated by deleting ads and analytics in the background, site by site.[82]

Leaked documents published by WikiLeaks, codenamed Vault 7 dated 2013–2016, details the features of the CIA, such as the ability to compromise web browsers (including Google Chrome).[83][84]

Malware blocking and ad blocking

Google introduced download verification protection in Chrome 17.[85] In February 2018, Google introduced a ad blocking resource based on recommendations from the Interactive Advertising Bureau. Sites that employ invasive ads receive a 30-day notice, after which their ads will be blocked.[86] Consumer Reports recommended users install dedicated ad blocking tools, which offer increased security against malware and tracking.[87]


  • Chrome supported, up to version 45, plug-ins with the Netscape Plugin application programming interface (NPAPI),[88] so that plug-ins (for example Adobe Flash Player) run as separate, unrestricted processes outside the browser and cannot be placed in the restricted area like tabs. ActiveX is not supported.[88] Since 2010, Adobe Flash is part of Chrome and does not need to be installed separately. Flash is updated as part of Chrome’s own updates.[89] Java Applet support was available on Chrome with Java 6, update 12 and above.[90] Support for Java on OS X was provided by an update to Java released on May 18, 2010.[91]
  • On August 12, 2009, Google introduced a replacement for NPAPI that is more portable and more secure[92] called pepper plugin API (PPAPI).[93] The included standard PPAPI Flash Player (or Pepper-based Flash Player) was available at Chrome OS first, then replaced the NPAPI Flash Player on Linux version 20 of Chrome, on Windows version 21 (which also reduced Flash crashes by 20%),[94] and finally came to OS X in version 23.[95]
  • On September 23, 2013, Google announced that it would deprecate and remove support for NPAPI. Support for NPAPI has been removed from Linux in version 35 of Chrome.[96] NPAPI plug-ins like Java can no longer work on Chrome (but there are workarounds for Flash using the PPAPI Flash Player on Linux, including Chromium).[97]
  • On April 14, 2015, Google released Chrome v42, disabling NPAPI by default. This makes plug-ins that do not have a PPAPI plug-in equivalent incompatible with Chrome, such as Java, light gray and unity. However, NPAPI support can be enabled using the chrome: // flags[[[[permanent dead link] menu, until the release of version 45 in September 2015, which completely removed support for NPAPI.[98]


Incognito mode

Google Chrome Incognito Message

The private browsing resource called Incognito The mode prevents the browser from permanently storing any story training, cookies, site data, or form entries.[99] The downloaded files and favorites will be stored. In addition, user activity is not hidden from the websites you visit or from your Internet service provider.

The incognito mode is similar to the private browsing feature in other web browsers. This does not prevent saving on all windows: “You can switch between an incognito window and any normal window you have opened. You will only be incognito when using the incognito window”.[100]

Listening resources

In June 2015, the Debian developer community found that Chromium 43 and Chrome 43 were programmed to download the Shared hotword module, which could allow the Ok google speech recognition extension, although by default it was “disabled”. This raised privacy concerns in the media.[101][102] The module was removed on Chrome 45, released on September 1, 2015 and was present only on Chrome 43 and 44.[103][104]

Concerns about user tracking

Chrome sends details about your users and their activities to Google through optional and non-optional user tracking mechanisms.[105][106]

Some of the tracking mechanisms can be optionally enabled and disabled via the installation interface[107] and through the browser options dialog.[108] Unofficial constructions, such as SRWare Iron, try to remove these browser features completely.[109] The RLZ feature is also not included in the Chromium browser.[110]

In March 2010, Google created a new method for collecting installation statistics: the unique ID token included in Chrome is now used only for the first connection that Google Update makes to your server.[111]

The optional suggestion service included with Google Chrome has been criticized because it provides the information entered in Omnibox to the search provider before the user returns. This allows the search engine to provide URL suggestions, but also to provide web usage information linked to a IP address.[112]

The optional feature to use a web service to help resolve spelling errors has privacy implications.[113]

Tracking methods
Method[109] Information sent When Optional? Choose to participate?
Installation Randomly generated token included in an installer; used to measure Google Chrome’s success rate once installed[114]

At installation

No N / A
RLZ identifier[115] Encoded the string, according to Google, contains non-identifying information from where Chrome was downloaded and its week of installation; it is used to measure promotional campaigns;[114] Google provides source code to decode this string[110]

It can be disabled in Chrome OS.[114] For Chrome browsers running on all other operating systems:[114]

  • Desktop versions of Chrome can prevent it by downloading the browser directly from Google.
  • Mobile versions of Chrome always send the RLZ identifier on the first launch.
  • In Google search query
  • First launch and first use of the address bar[114]
[note 2][114]
Customer ID[108] Unique identifier, along with user preferences, usage log metrics and failures Unknown yea[116] yea
Omnibox predictions[108] Text typed in Address bar When typing yea No
Page not found Text typed in the address bar Upon receiving the response “Server not found” yea No
Google update Information on how often Chrome is used, OS and Chrome version details Periodically Partial
[note 3][117]

Do not track

In February 2012, Google announced that Chrome would implement the Do not track (DNT) to inform websites that the user does not want to be tracked. The protocol was implemented in version 23. According to the draft of the W3 standard for DNT,[118] is disabled by default in Chrome.[119]


The Javascript virtual machine used by Chrome, the JavaScript V8 Engine, has features like dynamic code generation, hidden class transitionsand accurate garbage collection.[24]

In 2008, several sites conducted benchmark tests using the SunSpider JavaScript Reference tool, as well as Google’s own set of computationally intensive benchmarks, which include ray tracing and resolution of restrictions.[120] They unanimously reported that Chrome performed much faster than all the competitors it had been tested against, including Safari (for Windows), Firefox 3.0, Internet Explorer 7, Operaand Internet Explorer 8.[121][122][123][51][124][125] However, on October 11, 2010, independent tests of JavaScript performance, Chrome lagged behind only Opera’s Presto mechanism since it was updated in version 10.5.[126]

On September 3, 2008, Mozilla responded by stating that its own TraceMonkey The JavaScript engine (then in beta) was faster than Chrome’s V8 engine in some tests.[127][128][129] John Resig, Mozilla’s JavaScript evangelist, also commented on the performance of different browsers on Google’s own set, commenting on Chrome’s “decimation” of other browsers, but questioned whether the set of Google was representative of real programs. He stated that Firefox 3.0 performed poorly in recursion– intensive benchmarks, like those of Google, because the Mozilla team had not yet implemented recursion tracking.[130]

Two weeks after the launch of Chrome in 2008, the WebKit team announced a new JavaScript engine, SquirrelFish Extreme,[131] citing a 36% speed improvement over Chrome’s V8 engine.[132][133][134]

Like most major web browsers, Chrome uses DNS pre-search to speed up site searches,[135] just like other browsers like Firefox,[136] Safari,[137] Internet Explorer (called DNS pre-resolution),[138] is on Opera as a UserScript (not embedded).[139]

Chrome used to use its now discontinued SPDY protocol instead of just HTTP[140][141] when communicating with compatible servers, such as Google services, Facebook, Twitter. SPDY support has been removed in Chrome version 51. This was due to the replacement of SPDY by HTTP / 2, a standard that was based on it.

In November 2019, Google announced that it was working on several “quick flag” systems that tell visitors why a page is taking too long to appear. Variations include plain text warnings and more subtle signs that indicate that a site is slow. No date has been given for when the badge system will be included in the Chrome browser.[142]


Screenshot of a Chrome browser failure

A multi-process architecture is implemented in Chrome, where, by default, a separate process is allocated to each instance and plug-in of the website.[143] This procedure is called process isolation,[144] and prevents tasks from interfering with each other, increasing security and stability. An attacker who successfully gains access to an application gains access to none,[145] and failure in an instance results in a Sad Tab death screen, similar to the well-known Sad Mac, but only one tab crashes instead of the entire app. This strategy requires a fixed cost per process upfront, but results in less memory swelling over time, as fragmentation is confined to each instance and no longer requires additional memory allocations.[24] This architecture was adopted in Safari[146] and Firefox.[147]

Chrome includes a process management utility called Task Manager which allows users to see which sites and plug-ins are using the most memory, downloading most bytes and using too much CPU and provides the ability to complete them.[24] Chrome version 23 guarantees its users an improved battery life for systems that support Chrome GPU-accelerated video decoding.[148][45]

User interface

3D motif since its first public launch, September 2008 until March 2011

2D motif from March 2011 to October 2015

Material design reason used from September 2014 for mobile versions and October 2015 onwards for desktop versions

By default, the main user interface includes back, forward, update / cancel and menu buttons. A home button is not shown by default, but can be added via the Settings page to take the user to the new tab page or to a personalized home page.[149]

Guides are the main component of the Chrome user interface and have been moved to the top of the window and not below the controls. This subtle change contrasts with many browsers with existing tabs, based on windows and contains guides. The guides, with their status, can be transferred without interruption between the window containers by dragging. Each tab has its own set of controls, including the Omnibox.[24]

The Omnibox it is a Caixa URL que combina as funções da barra de endereço e da caixa de pesquisa. Se um usuário digitar o URL de um site pesquisado anteriormente, o Chrome permitirá pressionar Aba para pesquisar no site novamente diretamente da Omnibox. Quando um usuário começa a digitar na Omnibox, o Chrome fornece sugestões para sites visitados anteriormente (com base no URL ou no texto da página), sites populares (não necessariamente visitados anteriormente – com tecnologia da Google Instant) e pesquisas populares. Embora o Instant possa ser desativado, as sugestões baseadas em sites visitados anteriormente não podem ser desativadas. O Chrome também autocompletar os URLs dos sites visitados com frequência.[24] Se um usuário digitar palavras-chave na Omnibox que não correspondem a sites visitados anteriormente e pressionar Enter, o Chrome realizará a pesquisa usando o mecanismo de pesquisa padrão.

Um dos recursos diferenciadores do Chrome é o Página Nova guia, que pode substituir o navegador pagina inicial e é exibido quando uma nova guia é criada. Originalmente, isso mostrava miniaturas dos nove sites mais visitados, além de pesquisas frequentes, favoritos recentes e guias fechadas recentemente; igual a Internet Explorer and fire Fox with Barra de ferramentas do Googleor Opera’s Discagem rápida.[24] No Google Chrome 2.0, a página Nova guia foi atualizada para permitir que os usuários ocultem miniaturas que eles não desejam que apareçam.[150]

A partir da versão 3.0, a página Nova guia foi renovada para exibir miniaturas dos oito sites mais visitados. As miniaturas podem ser reorganizadas, fixadas e removidas. Como alternativa, uma lista de links de texto pode ser exibida em vez de miniaturas. Ele também possui uma barra “Recentemente fechada” que mostra as guias fechadas recentemente e uma seção “Dicas” que exibe dicas e truques para usar o navegador.[151]

O Chrome inclui um favoritos submenu que lista os favoritos do usuário, fornece acesso fácil aos Gerenciador de favoritos, e permite ao usuário alternar um Barra de favoritos ligado ou desligado.

For desenvolvedores web, O Chrome possui um inspetor de elementos (Inspect Element), semelhante ao Firebug extensão do navegador, que permite aos usuários pesquisar no DOM e ver o que compõe a página da web.[135]

O Chrome possui URLs especiais que carregam páginas específicas do aplicativo em vez de sites ou arquivos no disco. O Chrome também possui uma capacidade interna de habilitar recursos experimentais. Originalmente chamado about:labs, o endereço foi alterado para about:flags para tornar menos óbvio para usuários casuais.[152][153]

Em março de 2011, o Google introduziu um novo logotipo simplificado para substituir o logotipo 3D anterior usado desde o início do projeto. O designer do Google, Steve Rura, explicou o raciocínio da empresa: “Como o Chrome tem tudo a ver com tornar a sua experiência na Web o mais fácil e sem desordem possível, atualizamos o ícone do Chrome para representar melhor esses sentimentos. Um ícone mais simples incorpora o espírito do Chrome – para tornar a web mais rápida, mais leve e mais fácil para todos “.[154]

Em setembro de 2013, o Google começou a criar aplicativos Chrome “Para sua área de trabalho”. Isso significava acesso offline, atalhos da área de trabalho e menos dependência do Chrome – os aplicativos são iniciados em uma janela separada do Chrome e parecem mais com aplicativos nativos.[155]

Em 2 de janeiro de 2019, o Google introduziu o Native Dark Theme para Chrome no Windows 10.[156]

Atalhos e aplicativos da área de trabalho

Chrome permite que os usuários façam desktop local atalhos que aberto Aplicativos da web no navegador. O navegador, quando aberto dessa maneira, não contém nenhuma interface comum, exceto a barra de título, para não “interromper nada que o usuário esteja tentando fazer”. Isso permite que os aplicativos da Web sejam executados juntamente com o software local (semelhante ao Mozilla Prism and Fluido)[24]

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

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 extensions function simply as links to popular web pages and/or games, 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.[159]

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


Google Chrome Extensions are browser extensions that modify Google Chrome.[161] These extensions are written using web technologies like HTML, JavaScriptand CSS.[162] They are distributed through Chrome Web Store,[163] initially known as the Google Chrome Extensions Gallery.[161] All users with a Google Account are able to add extensions after developing them.[164] 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.[165] All extensions must have a clear and singular purpose.[166]

On September 9, 2009, Google enabled extensions by default on Chrome’s developer channel, and provided several sample extensions for testing.[167] In December, the Google Chrome Extensions Gallery beta began with approximately 300 extensions.[38][168] It was launched on January 25, 2010 along with Google Chrome 4.0, containing approximately 1500 extensions.[169]

In 2014, Google started preventing some Windows users from installing extensions not hosted on the Chrome Web Store.[170][171] The following year Google reported a “75% drop in customer support help requests for uninstalling unwanted extensions” which led them to expand this restriction to all Windows and Mac users.[172] Under the terms of the EULA, Google can remove or disable any extensions from a user’s installation of Chrome.[14]

Notable examples


Starting with Google Chrome 3.0, users can install themes to alter the appearance of the browser.[176] Many free third-party themes are provided in an online gallery,[177] accessible through a “Get themes” button in Chrome’s options.[178]

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.[179] When Chrome detects a foreign language other than the user’s preferred language as set during the installation time, it asks the user whether or not to translate.

Release channels, cycles and updates

The first production release on December 11, 2008, marked the end of the initial Beta test period and the beginning of production. Shortly thereafter, on January 8, 2009, Google announced an updated release system with three channels: Stable (corresponding to the traditional production), Beta, and Developer preview (also called the “Dev” channel). Where there were before only two channels: Beta and Developer, now there were three. Concurrently, all Developer channel users were moved to the Beta channel along with the promoted Developer release. Google explained that now the Developer channel builds would be less stable and polished than those from the initial Google Chrome’s Beta period. Beta users could opt back to the Developer channel as desired.

Each channel has its own release cycle and stability level. The Stable channel updated roughly quarterly, with features and fixes that passed “thorough” testing in the Beta channel. Beta updated roughly monthly, with “stable and complete” features migrated from the Developer channel. The Developer channel updated once or twice per week and was where ideas and features were first publicly exposed “(and sometimes fail) and can be very unstable at times”. [Quoted remarks from Google’s policy announcements.][180][181][182]

Google Chrome Canary Application Icon

On July 22, 2010, Google announced it would ramp up the speed at which it releases new stable versions; the release cycles were shortened from quarterly to six weeks for major Stable updates.[183] Beta channel releases now come roughly at the same rate as Stable releases, though approximately one month in advance, while Dev channel releases appear roughly once or twice weekly, allowing time for basic release-critical testing.[184] This faster release cycle also brought a fourth channel: the “Canary” channel, updated daily from a build produced at 09:00 UTC from the most stable of the last 40 revisions.[185] The name refers to the practice of using canaries in coal mines, so if a change “kills” Chrome Canary, it will be blocked from migrating down to the Developer channel, at least until fixed in a subsequent Canary build.[186] Canary is “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. This ensures that fallback functionality remains even when some Canary update may contain release-breaking bugs.[187] It does not natively include the option to be the default browser, although on Windows and OS X it can be set through System Preferences. Canary was Windows-only at first; The OS X version was released on May 3, 2011.[188]

The Chrome beta channel for Android was launched on January 10, 2013; like Canary, it runs side by side with the stable channel for Android.[189][190] Chrome Dev for Android was launched on April 29, 2015.[191]

All Chrome channels are automatically distributed according to their respective release cycles. The mechanism differs by platform. On Windows, it uses Google Update, and auto-update can be controlled via Group Policy.[192] Alternatively, users may download a standalone installer of a version of Chrome that does not auto-update.[193][194] On OS X, it uses Google Update Service, and auto-update can be controlled via the OS X “defaults” system.[195] On Linux, it lets the system’s normal package management system supply the updates. This auto-updating behavior is a key difference from Chromium, the non-branded open-source browser which forms the core of Google Chrome. Because Chromium also serves as the pre-release development trunk for Chrome, its revisions are provided as source code and buildable snapshots are produced continuously with each new commit, requiring users to manage their own browser updates.[196]

Release version numbers

Releases are identified by a four-part version number, e.g. 42.0.2311.90 (Windows Stable release April 14, 2015[197]) The components are[198][199]

Major.minor reflects scheduling policy
Build.patch identifies content progression
  • Major represents a product release. These are scheduled 7–8 per year, unlike other software systems where the major version number updates only with substantial new content.
  • Minor is usually 0. References to version ‘x’ or ‘x.0’, e.g. 42.0, refer to this major.minor designation.
  • Build is ever increasing. For a release cycle, e.g. 42.0, there are several builds in the Canary and Developer period. O último build number from Developer is kept throughout Beta and Stable and is locked with the major.minor for that release.
  • Patch resets with each build, incrementing with each patch. The first patch is 0, but usually the first publicly released patch is somewhat higher. In Beta and Stable, only patch increments.

Chromium and Chrome release schedules are linked through Chromium
(Major) version Branch Point dates, published annually.[198] The Branch Points precede the final Chrome Developer build (initial) release by 4 days (nearly always) and the Chrome Stable initial release by roughly 53 days.[200]

Example: The version 42 Branch Point was February 20, 2015.[198] Developer builds stopped advancing at build 2311 with release 42.0.2311.4 on February 24,[201] 4 days later. The first Stable release, 42.0.2311.90, was April 14, 2015,[197] 53 days after the Branch Point.

Color management

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


In Chrome, when not connected to the Internet and an error message displaying “No internet” is shown, on the top, an “8-bitTyrannosaurus rex is shown, but when pressing the space bar on a keyboard, mouse-clicking on it or tapping it on touch devices, the T-Rex instantly jumps once and dashes across a cactus-ridden desert, revealing it to be an Easter egg in the form of a platform game.[203][204][205][206] The game itself is an infinite runner, and there is no time limit in the game as it progresses faster and periodically tints to a black background. A school Chromebook administrator can disable the game.[207]


The current version of Chrome runs on:

As of April 2016, stable 32-bit and 64-bit builds are available for Windows, with only 64-bit stable builds available for Linux and Mac OS.[209][210][211] 64-bit Windows builds became available in the developer channel and as canary builds on June 3, 2014,[212] in the beta channel on July 30, 2014,[213] and in the stable channel on August 26, 2014.[214] 64-bit OS X builds became available as canary builds on November 7, 2013,[215][216] in the beta channel on October 9, 2014,[217] and in the stable channel on November 18, 2014.[209]


Operating system Latest version Support status
janelas 7 and later 80 2009–
XP and Vista 49. 2008–2016
Mac OS 10.10 and later 81 2014–
10.9 65 2013–2018
10.610.8 (x64) 49. 2010–2016
10.6 (IA-32) 38. 2010–2014
10.5 (IA-32,x64) 21 2010–2012
Linux desktop x64 80 2010–
IA-32 48 2010–2016
Android 4.4 and later 80 2013–
4.1-4.3 (ARMv7,IA-32,x64) 71[218] 2012–2019
4.0 (ARMv7,IA-32) 42. 2012–2015
iOS 12.0 and later 80 2018–
11.x 76 2017–2019
10.x 72 2016–2019
9.x , 8.x 63 2014–2018
7.x 54 2013–2016
6.x 42. 2012–2015
5.x 30 (For at least 512 MB of RAM)
23 (For 256 MB of RAM)
4.x 23 2012


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

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

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.[221][223] Also supports mobile oriented features such as Device Orientation and Geolocation.[223]

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

Features missing in the mobile version include sandboxed tabs,[221][224] Safe Browsing,[221] apps or extensions,[222] Adobe Flash (now and in the future),[222] Native Client.[222]

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

The April 17, 2012 update included availability 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.[226]

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

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

Starting from version 25, the Chrome version for Android is aligned with the desktop version, and usually new stable releases are available at the same time between the Android and the desktop version. Google released a separate Chrome for Android beta channel on January 10, 2013, with version 25.[189] As of 2013 a separate beta version of Chrome is available in the Google Play Store – it can run side by side with the stable release.[229]

Chrome OS

Google Chrome is the basis of Google’s Chrome OS operating system that ships on specific hardware from Google’s manufacturing partners.[230] 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.[231][232][233][234][235]

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


Chrome is available on maçã‘s mobile iOS operating system as Google Chrome for iOS. Released in the Apple App Store on June 26, 2012, it supports the iPad, iPhoneand iPod touch, and the current version requires that the device has iOS 12.0 or greater installed.[237] In accordance with Apple’s requirements for browsers released through their App Store, this version of Chrome uses the iOS WebKit – which is Apple’s own mobile rendering engine and components, developed for their Safari browser – therefore it is restricted from using Google’s own V8 JavaScript engine.[238][239] Chrome is the default web browser for the iOS Gmail application, but it cannot be used as the device-wide default application for opening webpages because Apple has not provided iOS users with the option to change the default from Safari.[240]

In a review by Chitika, Chrome was noted as having 1.5% of the iOS web browser market as of July 18, 2012.[241] In October 2013, Chrome had 3% of the iOS browser market.[242]


On Linux distributions, support for 32-bit Intel processors ended in March 2016 although Chromium is still supported.[243] As of Chrome version 26, Linux installations of the browser may be updated only on systems that support GCC v4.6 and GTK v2.24 or later. Thus deprecated systems include (for example) Debian 6’s 2.20, and RHEL 6’s 2.18.[244]


Support for Google Chrome on Windows XP and Windows Vista ended in April 2016.[245] The last release of Google Chrome that can be run on Windows XP and Windows Vista was version 49.0.2623.112,[246] released on April 7, 2016,[247] then re-released on April 11, 2016.[248]

Support for Google Chrome in Windows 7 will end on at least July 15, 2021.[249]

“Windows 8 mode” was introduced in 2012 and has since been discontinued. It was provided to the developer channel, which enabled Windows 8 and Windows 8.1 users to run Chrome with a full-screen, tablet-optimized interface, with access to snapping, sharing, and search functionalities.[250] In October 2013, Windows 8 mode on the developer channel changed to use a desktop environment mimicking the interface of Chrome OS with a dedicated windowing system and taskbar for web apps.[251] This was removed on version 49 and users that have upgraded to Windows 10 will lose this feature.[252]

Mac OS

Google dropped support for Mac OS X 10.5 with the release of Chrome 22.[253] Support for 32-bit versions of Chrome ended in October 2014 with the release of Chrome 39.[254][255][209] Support for Mac OS X 10.6, 10.7and 10.8 ended in April 2016 with the release of Chrome 50. Support for OS X 10.9 ended in April 2018 with the release of Chrome 66.[[[[citation needed]


Google Chrome was met with acclaim upon release. In 2008, Matthew Moore of The Daily Telegraph summarized the verdict of early reviewers: “Google Chrome is attractive, fast and has some impressive new features…”[256]

Initially, Microsoft reportedly played down the threat from Chrome and predicted that most people would embrace Internet Explorer 8. Opera Software said that “Chrome will strengthen the Web as the biggest application platform in the world”.[257] 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.”[258] 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.[259][260]

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.

With its dominance in the web browser market, Google has been accused of using Chrome and Blink development to push new web standards that are proposed in-house by Google and subsequently implemented by its services first and foremost. These have led to performance disadvantages and compatibility issues with competing browsers, and in some cases, developers intentionally refusing to test their websites on any other browser than Chrome.[262] Tom Warren of The Verge went as far as comparing Chrome to Internet Explorer 6, the default browser of Windows XP that was often targeted by competitors due to its similar ubiquity in the early 2000s.[263]

In 2019, Google similarly faced criticism over planned changes to its extensions API for Chrome (dubbed “Manifest V3”), which would inhibit the effectiveness of certain forms of ad blocking software by preventing the use of the WebRequest API to block and modify network connections. Google intends extensions to transition to another API known as DeclarativeWebRequest, which allows the extension to set up pre-configured rules that are processed by the browser itself rather than through the extension. However, concerns over how well the API would perform, in combination with concerns over a cap on the number of entries that may be blacklisted, led to criticism that these changes were designed to inhibit ad blocking (citing Google’s vested interest in the online advertising industry). Google cited performance issues associated with WebRequest, as it requires all network traffic to go through the extension before the page is loaded, as well as its use in malicious extensions, as justification for these changes. In June 2019, it announced that it would increase the aforementioned cap from 30,000 to 150,000 entries to help quell concerns.[264][265][266]


Market share

The most used web browser per country in 2019[268]

Chrome overtook fire Fox in November 2011, in worldwide usage. As of June 2016, according to StatCounter, Google Chrome had 62% worldwide desktop usage share, making it the most widely used web browser, while Firefox had 16% and Internet Explorer had 12%.[269][270]

Along with Safari and Mozilla Firefox, Chrome receives a weekend “bump”, which boosts its market share by as much as three percentage points on weekends, at the expense of Internet Explorer.[271]

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%.[272]

From May 14–21, 2012, Google Chrome was for the first time responsible for more Internet traffic than Microsoft’s Internet Explorer, which long had held its spot as the most used web browser in the world.[273] 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 had topped Internet Explorer for a single day’s usage in the past, this was the first time it had led for one full week.[274]

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

In June 2013, according to StatCounter, Chrome overtook Internet Explorer for the first time in the US.[276]

In August 2013, Chrome was used by 43% of internet users worldwide. This study was done by Statista, which also noted that in North America, 36% of people use Chrome, the lowest in the world.[277]

As of February 2018, Chrome is the most used browser in virtually all countries, with most exceptions in Africa.[279]

Enterprise deployment

In December 2010, Google announced that to make it easier for businesses to use Chrome they would provide an official Chrome MSI package. For business use it is helpful to have full-fledged MSI packages that can be customized via transform files (.mst) – but the MSI provided with Chrome is only a very limited MSI wrapper fitted around the normal installer, and many businesses find that this arrangement does not meet their needs.[280] 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[281] – it was formerly possible only when Chrome was installed using Google Pack. Google also created group policy objects to fine-tune the behavior of Chrome in the business environment, for example by setting automatic updates interval, disabling auto-updates, and configuring a home page.[282] Until version 24 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.[283]


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 and Linux operational systems. The Google-authored portion of Chromium is released under the permissive BSD license.[284] Other portions of the source code are subject to a variety of open-source licenses.[285] Chromium is similar to Chrome, but lacks built-in automatic updates and a built-in Flash player, as well as Google branding and has a blue-colored logo instead of the multicolored Google logo.[286][287] Chromium does not implement user RLZ tracking.[110][105][288] Initially, the Google Chrome PDF viewer, PDFium, was excluded from Chromium, but was later made open-source in May 2014.[289][290] PDFium can be used to fill PDF forms.[291]

Developing for Chrome

It is possible to develop applications, extensions, and themes for Chrome. They are zipped in a .crx file and contain a manifest file that specifies basic information (such as version, name, description, privileges, etc.), and other files for the user interface (icons, popups, etc.). Google has an official developer’s guide.[292] Chrome has its own web store where users and developers can upload and download these applications and extensions.[293]

Veja também



  1. ^ “Stable Channel Update for Desktop”. Chrome Releases. Blogger. 7 de abril de 2020. Retrieved April 7, 2020.
  2. ^ “Chrome for Android Update”. Chrome Releases blog. Blogger. 7 de abril de 2020. Retrieved April 7, 2020.
  3. ^ “Google Chrome on the App Store”. iTunes Preview. 7 de abril de 2020. Retrieved April 7, 2020.
  4. ^ “Beta Channel Update for Desktop”. Google Blogspot. April 2, 2020. Retrieved April 3, 2020.
  5. ^ “Chrome Beta for Android Update [date mislabeled as “Monday, April 6, 2020″]”. Google Blogspot. 7 de abril de 2020. Retrieved April 7, 2020.
  6. ^ uma b c d and “Google Chrome”. OmahaProxy CSV Viewer. Chromium team.
  7. ^ “Dev Channel Update for Desktop”. Google Blogspot. 8 de abril de 2020. Retrieved April 8, 2020.
  8. ^ “Chromium (Google Chrome)”. Retrieved February 8, 2012.
  9. ^ “Chromium coding style”. Google Open Source. Retrieved March 29, 2017.
  10. ^ Lextrait, Vincent (January 2010). “The Programming Languages Beacon, v10.0”. Archived from the original on May 30, 2012. Retrieved March 14, 2010.
  11. ^ “Google Chrome for Android is dropping support for Android 4.1-4.3 Jelly Bean”. XDA Developers. October 5, 2018. Retrieved December 10, 2018.
  12. ^ “Chrome for iOS”.
  13. ^ “Supported languages”. Google Play Console Help. Retrieved December 18, 2015.
  14. ^ uma b c d “Google Chrome Terms of Service”.
  15. ^ uma b Bright, Peter (April 3, 2013). “Google going its own way, forking WebKit rendering engine”. Ars Technica. Conde Nast. Retrieved March 9, 2017.
  16. ^ “Desktop Browser Market Share Worldwide”. StatCounter Global Stats. Retrieved April 5, 2020.
  17. ^ “Browser Market Share Worldwide”. StatCounter Global Stats. Retrieved April 5, 2020.
  18. ^ Angwin, Julia (July 9, 2009). “Sun Valley: Schmidt Didn’t Want to Build Chrome Initially, He Says”. WSJ Digits Blog. Retrieved May 25, 2010.
  19. ^ “Rumours surround Google browser”.
  20. ^ Bhardwaj, Prachi (June 29, 2018). “Larry Page has a reputation for pushing people at Google”. Business Insider. Retrieved January 3, 2020.
  21. ^ McCloud, Scott (September 1, 2008). “Surprise!”. Google Blogoscoped. Retrieved September 1, 2008.
  22. ^ Lenssen, Philipp (September 1, 2008). “Google Chrome, Google’s Browser Project”. Retrieved September 1, 2008.
  23. ^ Lenssen, Philipp (September 1, 2008). “Google on Google Chrome – comic book”. Google Blogoscoped. Retrieved September 1, 2008.
  24. ^ uma b c d and f g h i j k “Google Chrome comic”. Google Book Search. September 1, 2008. Retrieved September 2, 2008.
  25. ^ uma b Pichai, Sundar; Upson, Linus (September 1, 2008). “A fresh take on the browser”. Official Google Blog. Retrieved March 9, 2017.
  26. ^ Dougerty, Conor (July 12, 2015). “Sundar Pichai of Google Talks About Phone Intrusion”. New York Times. Archived from the original on July 19, 2015. Retrieved April 25, 2019.
  27. ^ “Google Chrome – The reason behind its name revealed!”. The Windows Club. Retrieved September 3, 2015.
  28. ^ “It was when not if… Google Chrome”. September 2008. Archived from the original on December 8, 2016. Retrieved June 21, 2017.CS1 maint: unfit url (link)
  29. ^ Fried, Ina (October 7, 2008). “Be sure to read Chrome’s fine print”. CNET. CBS Interactive. Retrieved March 9, 2017.
  30. ^ “Google Terms of Service – Policies & Principles – Google”. March 1, 2012. Retrieved March 30, 2013.
  31. ^ Needleman, Rafe (September 2, 2008). “Google Chrome update: First screenshot, and live-blog alert”. CNET. CBS Interactive. Retrieved March 9, 2017.
  32. ^ “Google launches Chrome web browser”. The Canadian Press. Associated Press. September 2, 2008. Retrieved September 2, 2008.
  33. ^ Gruener, Wolfgang (January 3, 2009). “Google Chrome crosses 1% market share again”. Chicago (IL), United States: TG Daily. Archived from the original on March 10, 2009. Retrieved July 11, 2012.
  34. ^ Shankland, Stephen (January 9, 2009). “Chrome gets Mac deadline, extensions foundation”. CNET. CBS Interactive. Retrieved March 9, 2017.
  35. ^ “Early Access Release Channels”. Retrieved April 8, 2012.
  36. ^ “Danger: Mac and Linux builds available”. Retrieved June 9, 2009.
  37. ^ Larson, Mark (December 8, 2009). “Beta Update: Linux, Mac, and Windows”. Chrome Releases. Retrieved March 9, 2017.
  38. ^ uma b Rakowski, Brian (December 8, 2009). “Google Chrome for the holidays: Mac, Linux and extensions in beta”. Official Google Blog. Retrieved March 9, 2017.
  39. ^ Rakowski, Brian (May 25, 2010). “A new Chrome stable release: Welcome, Mac and Linux!”. Chrome Blog. Retrieved March 9, 2017.
  40. ^ “Microsoft offers browser choices to Europeans”. BBC News. March 1, 2010. Retrieved July 11, 2012.
  41. ^ “NPAPI deprecation: developer guide – The Chromium Projects”. Retrieved September 3, 2015.
  42. ^ Krumins, Peteris (September 5, 2008). “Code reuse in Google Chrome Browser”. Retrieved May 13, 2010.
  43. ^ Fette, Ian (February 19, 2010). “Hello HTML5”. Retrieved July 11, 2012.
  44. ^ “HTML Video Codec Support in Chrome”. January 11, 2011. Retrieved April 8, 2012.
  45. ^ uma b Fischmann, Ami (November 6, 2012). “Longer battery life and easier website permissions”. Chrome Blog. Retrieved March 9, 2017.
  46. ^ Trollope, Rowan (December 22, 2013). “Open-Sourced H.264 Removes Barriers to WebRTC”. Archived from the original on July 6, 2015. Retrieved December 22, 2013.
  47. ^ “Google Chrome Beta arrives on Android”. Engadget. AOL. Retrieved July 11, 2012.
  48. ^ “Chrome Out Of Beta, Default Browser Of Android 4.1”.
  49. ^ Matney, Lucas. “Chrome is coming to augmented reality and Google Daydream”.
  50. ^ Needleman, Rafe (June 12, 2008). “The future of the Firefox address bar”. CNET. CBS Interactive. Retrieved March 9, 2017.
  51. ^ uma b Shankland, Stephen (October 7, 2008). “Speed test: Google Chrome beats Firefox, IE, Safari”. CNET. CBS Interactive. Retrieved March 9, 2017.
  52. ^ Purdy, Kevin (June 11, 2009). “Lifehacker Speed Tests: Safari 4, Chrome 2, and More – Browsers”. Lifehacker. Retrieved May 13, 2010.
  53. ^ Laforge, Anthony. “Stable Channel Update”. Retrieved May 25, 2010.
  54. ^ “ECMAScript test262”. Archived from the original on May 14, 2011. Retrieved May 6, 2011.
  55. ^ “CSS 2.1 Test Suite RC6 Results”. W3C. Retrieved May 6, 2011.
  56. ^ “HTML5 test desktop”. Visred. Retrieved March 19, 2015.
  57. ^ “HTML5 test desktop browser comparison”. Visred. Retrieved March 19, 2015.
  58. ^ “HTML5 test Android Chrome 41 Galaxy S5”. Visred. Retrieved March 19, 2015.
  59. ^ “HTML5 test tablet”. Sights. Retrieved March 19, 2015.
  60. ^ “HTML5 test mobile”. Sights. Retrieved March 19, 2015.
  61. ^ “HTML5test – How well does your browser support HTML5?”. Retrieved October 29, 2015.
  62. ^ Chung, Marc (September 5, 2008). “chromes-process model explained”. Archived from the original on March 21, 2009. Retrieved September 10, 2008.
  63. ^ Barth, Adam; Jackson, Collin; Reis, Charles; The Google Chrome Team. “The Security Architecture of the Chromium Browser” (PDF). Stanford Security Laboratory. Retrieved September 11, 2008.
  64. ^ Gutschke, Markus (May 6, 2009). “Re: (PATCH 2/2) x86-64: seccomp: fix 32/64 syscall hole”. Archived from the original on June 24, 2013. Retrieved February 17, 2011.
  65. ^ Edge, Jake (August 19, 2009). “Google’s Chromium sandbox”. Retrieved February 17, 2011.
  66. ^ Huge Security Flaw Leaks VPN Users’ Real IP-addresses (January 30, 2015). Retrieved on February 21, 2015.
  67. ^ Bates, Adam. “InsightPortal | QualityTaskForce | Chrome will start flagging insecure HTTP sites”. Retrieved August 8, 2017.
  68. ^ Cimpanu, Catalin, ZDNet. “Google releases Chrome 71 with a focus on security features.” December 4, 2018. Retrieved January 2, 2019.
  69. ^ “Issue 53 – chromium – No Master Password Option”. September 2, 2008. Retrieved August 13, 2013.
  70. ^ Kember, Elliott (August 7, 2013). “Chrome’s Password Security Strategy Is Insane”. Retrieved August 13, 2013.
  71. ^ “Issue 53 – chromium – No Master Password Option (post #151)”. Retrieved May 3, 2014.
  72. ^ “Linux Password Storage”. Retrieved December 25, 2019.
  73. ^ “OS X Password Manager/Keychain Integration”. Retrieved December 25, 2019.
  74. ^ Keizer, Gregg (March 10, 2011). “Google’s Chrome untouched at Pwn2Own hack match”. Computerworld.
  75. ^ uma b “Pwn2Own 2012: Google Chrome browser sandbox first to fall”. ZDNet. CBS Interactive. March 7, 2012. Retrieved April 8, 2012.
  76. ^ “CanSecWest Pwnium: Google Chrome hacked with sandbox bypass”. ZDNet. CBS Interactive. March 7, 2012. Retrieved April 8, 2012.
  77. ^ “Teenager hacks Google Chrome with three 0day vulnerabilities”. ZDNet. CBS Interactive. March 9, 2012. Retrieved April 8, 2012.
  78. ^ Kersey, Jason (March 10, 2012). “Chrome Stable Update”. Retrieved March 10, 2012.
  79. ^ Goodin, Dan (October 10, 2012). “Google Chrome exploit fetches “Pinkie Pie” $60,000 hacking prize”. Ars Technica. Condé Nast. Retrieved March 9, 2017.
  80. ^ “Pwnium 2: results and wrap-up”. Chromium Blog. October 10, 2012.
  81. ^ “Pwn2own Day 1 Exploits: Google Chrome, Adobe Flash, Apple Safari”. Retrieved September 20, 2016.
  82. ^ “Google targets HTML5 default for Chrome instead of Flash in Q4 2016”. VentureBeat. Retrieved September 20, 2016.
  83. ^ “WikiLeaks posts trove of CIA documents detailing mass hacking”. CBS News. March 7, 2017.
  84. ^ Greenberg, Andy (March 7, 2017). “How the CIA Can Hack Your Phone, PC, and TV (Says WikiLeaks)”. Wired (magazine).
  85. ^ “Chrome Browser”. Retrieved April 21, 2014.
  86. ^ Tsukayama, Hayley (February 15, 2018). “Google’s Chrome ad blocker means the Web’s largest ad company is also now advertising’s biggest traffic cop”. The Washington Post. Retrieved February 15, 2018.
  87. ^ Chaikivsky, Andrew (February 15, 2018). “Want to Protect Against Websites That Spy on You? Get an Ad Blocker”. Consumer Reports. Retrieved February 15, 2018.
  88. ^ uma b “Google Chrome FAQ for web developers”. Archived from the original on September 4, 2008. Retrieved April 8, 2012.
  89. ^ Paul, Ryan (March 2010). “Google bakes Flash into Chrome, hopes to improve plug-in API”. Retrieved March 14, 2010.
  90. ^ “Java and Google Chrome”. Retrieved December 11, 2009.
  91. ^ “Issue 10812 – chromium – No java plugin support yet”. Retrieved May 18, 2010.
  92. ^ “”. February 24, 2012. Retrieved March 23, 2013.
  93. ^ “Pepper Plugin API (PPAPI)”. Retrieved March 23, 2013.
  94. ^ “Chromium Blog: The road to safer, more stable, and flashier Flash”. August 8, 2012. Retrieved August 29, 2012.
  95. ^ “Securing Flash Player for our Mac users”. Retrieved November 14, 2012.
  96. ^ “Chromium Blog: Saying Goodbye to Our Old Friend NPAPI”. Chromium Blog. Retrieved July 13, 2015.
  97. ^ “PSA: Chrome for Linux planning to drop NPAPI support as soon as April”. Retrieved April 22, 2015. Another thing I found last night is a Debian package called PepperFlashPlayer. Apparently it works the same way as the existing FlashPlayer package (which downloads Adobe Flash from Adobe and installs it) — it downloads Chrome from Google, extracts the PPAPI Flash plugin, and installs it for Chromium. That might be a good work-around for Chromium users in the interim. (Note: I am not endorsing this method, just making people aware of it.) But obviously it would be better if PPAPI Flash were available in a more “official” context.
  98. ^ “NPAPI deprecation: developer guide”.
  99. ^ “Browse in private – Computer – Google Chrome Help”. Retrieved April 1, 2018.
  100. ^ “Explore Google Chrome Features: Incognito Mode”. September 2, 2008. Retrieved September 4, 2008.
  101. ^ Falkvinge, Rick (June 18, 2015). “Google Chrome Listening In To Your Room Shows The Importance Of Privacy Defense In Depth”. Private Internet Access Blog. Retrieved April 7, 2018.
  102. ^ Bright, Peter. “Not OK, Google: Chromium voice extension pulled after spying concerns”. Ars Technica. Retrieved April 7, 2018.
  103. ^ “Diff – 0366a5184a70b3eefb5fcef2c2e13721669f00d8^! – chromium/src – Git at Google”. Retrieved September 26, 2017.
  104. ^ “Chrome Releases: Stable Channel Update”. Retrieved September 1, 2015.
  105. ^ uma b “Google Chrome, Chromium, and Google”. The Chromium Blog. October 1, 2008.
  106. ^ “Welcome to the Botnet”. April 7, 2018. Archived from the original on April 7, 2018. Retrieved April 7, 2018.
  107. ^ “Google Chrome Privacy Notice”. December 13, 2011. Retrieved February 4, 2012.
  108. ^ uma b c “Google Reacts to Some Chrome Privacy Concerns”. Retrieved September 24, 2008.
  109. ^ uma b “SRWare Iron webpage”. Retrieved October 12, 2008.
  110. ^ uma b c “In The Open, For RLZ”. The Chromium Blog. June 2, 2010. Retrieved June 20, 2010.
  111. ^ “Google Chrome Unique Identifier Change”. March 16, 2010. Retrieved March 24, 2010.
  112. ^ Fried, Ina (October 7, 2008). “Google’s Omnibox could be Pandora’s box”. CNET. CBS Interactive. Retrieved March 9, 2017.
  113. ^ “Chrome’s privacy settings”. Retrieved April 25, 2013.
  114. ^ uma b c d and f “Google Chrome Privacy Whitepaper” (PDF). Retrieved April 8, 2012.
  115. ^ “&rlz= in Google referrer: Organic traffic or AdWords?”. Retrieved February 27, 2009.
  116. ^ Controlled by the setting “Send usage statistics and error reports”; default off
  117. ^ “Turning Off Auto Updates in Google Chrome”. Retrieved December 12, 2014.
  118. ^ “Tracking DNT”. W3C. Retrieved December 17, 2015.
  119. ^ “Google and Chrome To Support Do Not Track”. Archived from the original on February 26, 2012. Retrieved March 3, 2012.
  120. ^ “V8 Benchmark suite”. Google Code. Archived from the original on September 4, 2008. Retrieved September 3, 2008.
  121. ^ Goodwins, Rupert (September 2, 2008). “Google Chrome – first benchmarks. Summary: wow”. Archived from the original on September 3, 2008.
  122. ^ “Google Chrome Javascript Benchmarks”. September 1, 2008. Archived from the original on January 7, 2012. Retrieved April 8, 2012.
  123. ^ Kingsley-Hughes, Adrian (September 2, 2008). “Google Chrome is insanely fast … faster than Firefox 3.0”. ZDNet. CBS Interactive.
  124. ^ Limi, Alexander (September 2, 2008). “Chrome: Benchmarks and more”. Archived from the original on April 24, 2010. Retrieved May 13, 2010.
  125. ^ Lipskas, Vygantas (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.
  126. ^ Scott M. Fulton, III (October 11, 2010). “Firefox in the dust: Opera poised to reclaim browser performance lead”. Archived from the original on July 14, 2011. Retrieved November 6, 2010.
  127. ^ Shankland, Stephen (October 7, 2008). “Firefox counters Google’s browser speed test”. CNET. CBS Interactive. Retrieved March 9, 2017.
  128. ^ Eich, Brendan (September 3, 2008). “TraceMonkey Update”.
  129. ^ Shankland, Stephen (November 3, 2008). “Third Chrome beta another notch faster – News”. Builder AU. Retrieved May 13, 2010.
  130. ^ Resig, John (September 3, 2008). “JavaScript Performance Rundown”.
  131. ^ Stachowiak, Maciej (September 18, 2008). “WebKit blog: Introducing SquirrelFish Extreme”. Retrieved May 13, 2010.
  132. ^ Zwarich, Cameron (September 18, 2008). “SquirrelFish Extreme has landed!”. Archived from the original on April 27, 2009. Retrieved May 13, 2010.
  133. ^ Shankland, Stephen (September 22, 2008). “Step aside, Chrome, for Squirrelfish Extreme – News”. Builder AU. Retrieved May 13, 2010.
  134. ^ Ying, Charles (September 19, 2008). “SquirrelFish Extreme: Fastest JavaScript Engine Yet”. Retrieved May 13, 2010.
  135. ^ uma b Gralla, Preston (September 3, 2008). “Three hidden Chrome features you’ll love”. Archived from the original on September 23, 2008. Retrieved September 16, 2008.
  136. ^ “DNS prefetching for Firefox”. November 8, 2008.
  137. ^ Apple Inc. (June 7, 2010). “What’s new in Safari 5”. Retrieved July 6, 2010.
  138. ^ “Internet Explorer 9 Network Performance Improvements”. March 17, 2011. Retrieved April 8, 2012.
  139. ^ Eiras, João. “Page prefetcher”. Retrieved April 8, 2012.
  140. ^ “chrome]Index of /trunk/src/net/spdy – Chromium SPDY client implementation”. Retrieved April 8, 2012.
  141. ^ “SPDY Proxy Examples – The Chromium Projects”. Retrieved April 8, 2012.
  142. ^ “Moving towards a faster web”. Chromium Blog. November 11, 2019.
  143. ^ Reisn, Charlie (September 11, 2008). “Multi-process Architecture”. Retrieved September 12, 2008.
  144. ^ “Process Models”. The Chromium Projects. September 3, 2008. Retrieved September 12, 2008.
  145. ^ Prince, Brian (December 11, 2008). “Google Chrome Puts Security in a Sandbox”. Ziff Davis Enterprise Holdings Inc. Retrieved June 4, 2010.
  146. ^ “[webkit-dev] Announcing WebKit2”. Retrieved April 8, 2012.
  147. ^ “Firefox Lorentz beta available for download and testing”. Mozilla. April 8, 2010.
  148. ^ “Chrome 23 Closes 15 Security Vulnerabilities, Promises Longer Battery Life & Added Do Not Track (DNT)”. Retrieved November 9, 2012.
  149. ^ Google (2012). “Set your home page”. Retrieved May 22, 2012.
  150. ^ Fisher, Darin (May 21, 2009). “A Speedier Google Chrome for all users”. Chrome Blog. Retrieved March 9, 2017.
  151. ^ LaForge, Anthony (September 15, 2009). “Google Chrome after a year: Sporting a new stable release”. Official Google Blog. Retrieved March 9, 2017.
  152. ^ “Chromium”. Archived from the original on September 8, 2010. Retrieved September 1, 2010.
  153. ^ Pash, Adam (October 2010). “Chrome’s About:Labs Renamed to About:Flags, Adds a Warning”. LifeHacker. Retrieved October 19, 2010.
  154. ^ Rura, Steve (March 2011). “A fresh take on an icon”. Retrieved March 22, 2011.
  155. ^ Kay, Erik (September 5, 2013). “A new breed of Chrome Apps”. Chrome Blog. Retrieved March 9, 2017.
  156. ^ Danica Simic, ValueWalk. “Google To Introduce Native Dark Theme For Chrome On Windows 10.” January 2, 2019. Retrieved January 4, 2019.
  157. ^ “Chrome Web Store”. May 19, 2010. Retrieved May 24, 2010.
  158. ^ Lay, Erik (May 19, 2010). “The Chrome Web Store”. Retrieved May 24, 2010.
  159. ^ Paul, Ryan (December 9, 2010). “Chrome Web Store: a solution in search of a problem?”. Ars Technica. Condé Nast. Retrieved March 9, 2017.
  160. ^ Kay, Erik; Boodman, Aaron (February 3, 2011). “A dash of speed, 3D and apps”. Chrome Blog. Retrieved March 9, 2017.
  161. ^ uma b Rakowski, Brian (December 8, 2009). “Google Chrome Extensions Blog Announcement”. Retrieved February 25, 2010.
  162. ^ “Google Chrome Extensions Help Page”. Archived from the original on February 8, 2010. Retrieved February 25, 2010.
  163. ^
    Nield, David (April 20, 2012). “20 best Chrome extensions”. TechRadar. Archived from the original on May 3, 2012. Retrieved May 16, 2012.
  164. ^ “Publish in the Chrome Web Store”. Retrieved September 7, 2018.
  165. ^ “Chrome Web Store Help”. Retrieved April 8, 2012.
  166. ^ D’Orazio, Dante (December 20, 2013). “New Chrome Web Store rules demand extensions ‘have a single purpose. The Verge. Retrieved October 12, 2019.
  167. ^ Boodman, Aaron (September 9, 2009). “Extensions Status: On the Runway, Getting Ready for Take-Off”. Retrieved May 13, 2010.
  168. ^ Kay, Erik (December 8, 2009). “Extensions beta launched, with over 300 extensions!”. Retrieved May 13, 2010.
  169. ^ Baum, Nick (January 25, 2010). “Over 1,500 new features for Google Chrome”. Chrome Blog. Retrieved March 9, 2017.
  170. ^ “Chrome For Windows Will Now Only Install Extensions From Google’s Web Store”. TechCrunch. Retrieved December 14, 2018.
  171. ^ “Protecting Chrome users from malicious extensions”. Google Chrome Blog. Retrieved December 14, 2018.
  172. ^ “Continuing to protect Chrome users from malicious extensions”. Chromium Blog. Retrieved December 15, 2018.
  173. ^ “Chrome Web Store – Adblock Plus (Beta)”. Retrieved May 16, 2012.
  174. ^ “Chrome Web Store – Facebook Messenger”. Retrieved January 1, 2014.
  175. ^ “Chrome Web Store – uBlock Origin”. Retrieved May 16, 2012.
  176. ^ Murphy, Glen; Sabec, Mark (October 5, 2009). “A splash of color to your browser: Artist Themes for Google Chrome”. Chrome Blog. Retrieved March 9, 2017.
  177. ^ “Chrome Web Store”. Retrieved April 8, 2012.
  178. ^ “Basic settings: Change browser theme”. Google Chrome Help.
  179. ^ “Change Chrome languages & translate webpages”.
  180. ^ Larson, Mark (January 8, 2009). “Google Chrome Release Channels”. Retrieved January 9, 2009.
  181. ^ Larson, Mark (January 8, 2009). “Dev update: New WebKit version, new features, and a new Dev channel”. Retrieved January 9, 2009.
  182. ^ Fette, Ian (December 11, 2008). “Thanks For All Your Help”. Retrieved May 1, 2015.
  183. ^ Laforge, Anthony (July 22, 2010). “Release Early, Release Often”. Retrieved July 25, 2010.
  184. ^ The Chromium Authors. “Chrome Release Channels”. Retrieved October 29, 2014.
  185. ^ Irish, Paul (November 2, 2012). “Chrome Canary for Developers”. Retrieved October 29, 2014.
  186. ^ Bridge, Henry (August 2, 2010). “Google Chrome in a Coal Mine”. Chromium Blog. Retrieved March 19, 2015.
  187. ^ Mathews, Lee (July 23, 2010). “Google drops Chrome Canary build down the Chrome mineshaft”. Archived from the original on July 25, 2010. Retrieved July 25, 2010.
  188. ^ “Adding more yellow to the Mac color scheme”. May 2, 2011. Retrieved February 4, 2012..
  189. ^ uma b Protalinski, Emil (January 10, 2013). “Google launches Chrome Beta channel for Android 4.0+ phones and tablets, releases version 25”. The Next Web. Retrieved March 9, 2017.
  190. ^ “Chrome beta for Android on Google Play”. Retrieved March 23, 2013.
  191. ^ “Google Launches Dev Channel for Chrome on Android”. Chrome Story. Retrieved July 13, 2015.
  192. ^ Dorwin, David (May 14, 2009). “Google Update Releases Update Controls”. Retrieved May 13, 2010.
  193. ^ “Alternate (offline) Google Chrome installers for Windows – Chrome Help”.
  194. ^ “Get a fast, free web browser”. Retrieved February 17, 2017.
  195. ^ “Google Help page “Managing updates in Google Software Update.
  196. ^ “Tour of the Chromium Buildbot Waterfall – The Chromium Projects”. Retrieved December 2, 2014.
  197. ^ uma b “Version 42 Stable Release”. Chrome Releases. April 14, 2015. Retrieved December 28, 2015.
  198. ^ uma b c “Chromium Development Calendar and Release Info”. The Chromium Projects. Retrieved May 1, 2015.
  199. ^ Mike Frysinger (March 14, 2014). “Version Numbers”. The Chromium Projects. Retrieved May 1, 2015.
  200. ^ Anthony LaForge (December 16, 2010). “Chrome Release Cycle -12/16/2010”. Google Slides. Retrieved May 1, 2015.
  201. ^ “Version 42 Developer Update”. Chrome Releases. February 26, 2015. Retrieved December 28, 2015.
  202. ^ “Issue 143: Handle color profiles in tagged images”. September 2, 2008. Retrieved March 23, 2013.
  203. ^ “Google Chrome Easter Egg T-Rex Mini Game”. Business Insider.
  204. ^ “Play Google Chrome’s Secret Offline Game”.
  205. ^ “How do I find the secret dinosaur game on Google Chrome when my internet connection is down?”. RadioTimes.
  206. ^ “Google Chrome’s ‘Unable to connect to the Internet’ page has a hidden endless runner game”. The Independent.
  207. ^ “Issue 462221 – chromium – Disable offline game (T-Rex) if device is enrolled – Monorail”. February 26, 2015. Retrieved July 27, 2016.
  208. ^ uma b c “Download and install Google Chrome”. Google Help. See system requirements. Retrieved April 20, 2016.
  209. ^ uma b c Google (November 18, 2014). “Stable Channel Update”. Retrieved November 18, 2014.
  210. ^ Google. “64-bit Support – The Chromium Projects”. Retrieved March 5, 2012.
  211. ^ “Download Chrome for Linux”.
  212. ^ Google. “Try out the new 64-bit Windows Canary and Dev channels”. Retrieved July 1, 2014.
  213. ^ Google. “Announcing the Chrome 64-bit Beta Channel for Windows!”. Retrieved August 11, 2014.
  214. ^ “64 bits of awesome: 64-bit Windows Support, now in Stable!”. August 26, 2014. Retrieved August 27, 2014.
  215. ^ Google. “[chromium-dev] Yesterday’s Mac canary was 64-bit”. Retrieved July 1, 2014.
  216. ^ Google. “Re: [chromium-dev] Re: Chromium 64-bit on Mac OS”. Retrieved July 1, 2014.
  217. ^ Google (October 9, 2014). “Beta Channel Update”. Retrieved October 10, 2014.
  218. ^ “Google Chrome for Android is dropping support for Android 4.1-4.3 Jelly Bean”. XDA Developers. October 5, 2018. Retrieved December 10, 2018.
  219. ^ “Install Chrome for Android Beta – Google Chrome Help”. Google Inc. Retrieved April 6, 2012.
  220. ^ uma b c “Beta version of Chrome for Android 4.0 released”. Retrieved February 9, 2012..
  221. ^ uma b c d and “Google Operating System: Chrome for Android”. February 27, 2004. Retrieved February 9, 2012..
  222. ^ uma b c d “Google Chrome for Android – 23 Questions and Answers”. Chrome Story. Retrieved February 9, 2012.
  223. ^ uma b c d and Beverloo, Peter (January 30, 2012). “Bringing Google Chrome to Android”. Retrieved February 9, 2012. .
  224. ^ “Security overview”. Google Inc. Retrieved February 9, 2012. .
  225. ^ “Google Chrome for Android: Remote Debugging”. Google Inc. Retrieved February 9, 2012. .
  226. ^ Lardinois, Frederic (April 17, 2012). “Chrome For Android Gets Desktop View, Home Screen Bookmarks, File Downloads”.
  227. ^ “Google Chrome for Android comes out of beta, Hits Play today”. Engadget. AOL. June 27, 2012. Retrieved June 27, 2012..
  228. ^ “Chrome for Android Update”. September 26, 2012. Retrieved March 23, 2013.
  229. ^ “Chrome Beta for Android”. May 26, 2013. Retrieved July 4, 2013.
  230. ^ 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. Condé Nast. Archived from the original on April 9, 2014. Retrieved November 22, 2009.
  231. ^ Sengupta, Caesar; Papakipos, Matt (November 19, 2009). “Releasing the Chromium OS open source project”. Official Google Blog. Retrieved March 9, 2017.
  232. ^ Stokes, Jon (January 20, 2010). “Google talks Chrome OS, HTML5, and the future of software”. Ars Technica. Condé Nast. Retrieved March 9, 2017.
  233. ^ Womack, Brian (July 8, 2009). “Google to Challenge Microsoft With Operating System”. Bloomberg. Retrieved July 8, 2009.
  234. ^ Hansell, Saul (July 8, 2009). “Would you miss Windows with a Google operating system?”. New York Times. Retrieved July 8, 2009.
  235. ^ Pichai, Sundar; Upson, Linus (July 7, 2009). “Introducing the Google Chrome OS”. Official Google Blog. Retrieved March 9, 2017.
  236. ^ Mediati, Nick (July 7, 2009). “Google Announces Chrome OS”. PC World. IDG. Retrieved July 8, 2009.
  237. ^ “Chrome entry – Apple’s App Store”.
  238. ^ “Google Chrome on iOS Hits #1 Free App”. Forbes.
  239. ^ “iOS 8 WebKit changes finally allow all apps to have the same performance as Safari”.
  240. ^ Kovach, Steve (May 8, 2013). “Here’s Even More Evidence That Google Is Trying To Take Over The iPhone”. Business Insider. Retrieved June 10, 2013.
  241. ^ Reisinger, Don (July 18, 2012). “Chrome already nabs 1.5 percent of iOS browser market”. CNET. CBS Interactive. Retrieved March 9, 2017.
  242. ^ “Chrome’s Share of iOS Usage Doubles Year-Over-Year to 3%”. Mac Rumors. October 11, 2013. Retrieved April 21, 2014.
  243. ^ “Google ends 32-bit Linux support for Chrome”. OSNews.
  244. ^ “Chrome stops declaring Linux systems obsolete – The H Open: News and Features”. February 14, 2013. Retrieved March 30, 2013.
  245. ^ Pawliger, Marc (November 10, 2015). “Updates to Chrome platform support”. Chrome Blog. Retrieved March 9, 2017.
  246. ^ Cunningham, Andrew (April 14, 2016). “Chrome 50 ends support for Windows XP, OS X 10.6, other old versions”. ArsTechnia. Archived from the original on May 5, 2016. Retrieved October 9, 2016.
  247. ^ “Stable Channel Update”. Retrieved August 10, 2016.
  248. ^ “Google Chrome 49.0.2623.112”. Retrieved August 10, 2016.
  249. ^ “How Chrome is helping enterprises still using Windows 7”. Google Cloud Blog. Retrieved January 15, 2020.
  250. ^ Newman, Jared. “Google Chrome Gets Early Metro-Style App for Windows 8”. PCWorld. IDG. Retrieved June 13, 2012.
  251. ^ “Google is building Chrome OS straight into Windows 8”. The Verge. Retrieved October 5, 2013.
  252. ^ “Unable to open Google Chrome in windows 8 mode – Google Product Forums”. Retrieved September 29, 2016.
  253. ^ “Chrome no longer supports Mac OS X 10.5”. Google Inc. Archived from the original on March 29, 2015.
  254. ^ “Chrome updates on Mac 32-bit”. Chrome help. Google Inc.
  255. ^ “Google to Discontinue 32-bit Chrome for Mac Next Month”. AMD! Chrome!.
  256. ^ Moore, Matthew (September 2, 2008). “Google Chrome browser: Review of reviews”. Daily Telegraph. Retrieved September 24, 2011.
  257. ^ Liedtke, Michael (September 3, 2008). “Google polishes product line with Chrome browser”. Associated Press. Archived from the original on June 23, 2012.
  258. ^ Jaroslovsky, Rich (February 25, 2010). “Browser Wars: The Sequel”. BusinessWeek.
  259. ^ “Thoughts on Chrome & More”. John’s Blog. September 1, 2008. Retrieved May 13, 2010.
  260. ^ Collins, Barry (September 2, 2008). “Mozilla: Google’s not trying to kill us”. PC Pro. Dennis Publishing. Archived from the original on February 10, 2009. Retrieved July 11, 2012.
  261. ^ Mediati, Nick (September 3, 2008). “Google Chrome Web Browser”. PC World. IDG. Retrieved September 7, 2008.
  262. ^ “Google’s Chrome Becomes Web ‘Gatekeeper’ and Rivals Complain”. Bloomberg. May 28, 2019. Retrieved May 28, 2019.
  263. ^ Warren, Tom (January 4, 2018). “Chrome is turning into the new Internet Explorer 6”. The Verge. Retrieved May 28, 2019.
  264. ^ Cimpanu, Catalin. “Google promises to play nice with ad blockers (again)”. ZDNet. Retrieved June 13, 2019.
  265. ^ Tung, Liam. “Google Chrome could soon kill off most ad-blocker extensions”. ZDNet. Retrieved June 13, 2019.
  266. ^ Mihalcik, Carrie. “Google says Chrome isn’t killing ad blockers”. CNET. Retrieved June 13, 2019.
  267. ^ “Top 5 Browsers from December 2010 to December 2011”. StatCounter. Retrieved January 8, 2012.
  268. ^ “Browser Market Share Worldwide – September 2019”. Statcounter. September 2019. Retrieved October 19, 2019.
  269. ^ “Top 9 Desktop Browsers from W01 2015 to W27 2016”. StatCounter.
  270. ^ For additional sources see Usage share of web browsers#Summary table
  271. ^ “Global Web Browser Marketshares”. Clicky Analytics. Retrieved April 8, 2012.
  272. ^ “Chrome is world’s number one browser for a day”. StatCounter. March 21, 2012.
  273. ^ “Chrome overtakes Internet Explorer as No. 1 browser — maybe”. CNN. May 21, 2012. Retrieved May 21, 2012.
  274. ^ Pachal, Peter (May 21, 2012). “Google Chrome Now the No. 1 Browser in the World”.
  275. ^ “Chrome tops 310 million users, almost 100% growth over last year”. June 28, 2012.
  276. ^ “Stats Counter US Monthly bar graph”. June 2013. Retrieved July 25, 2013.
  277. ^ Fox, Zoe (August 14, 2013). “43% of Global Web Surfers Choose Google Chrome”.
  278. ^ “Desktop Browser Market Share Worldwide”. StatCounter Global Stats. Retrieved November 23, 2019.
  279. ^ “Change MSI from a wrapper to “full” MSI”. January 4, 2011. Retrieved April 8, 2012.
  280. ^ Paul, Ryan (December 16, 2010). “Google offering MSI to simplify Chrome enterprise deployment”. Ars Technica. Condé Nast. Retrieved March 9, 2017.
  281. ^ “Google Update for Enterprise – Google Help”. Retrieved July 11, 2012.
  282. ^ “Issue 2423 – chromium – Windows Roaming Profile support – An open-source browser project to help move the web forward. – Google Project Hosting”. September 17, 2008. Retrieved April 8, 2012.
  283. ^ “Home (Chromium Developer Documentation)”. Chromium Developer Documentation. 2009. Retrieved May 5, 2009.
  284. ^ “Chromium Terms and Conditions”. Google Code. September 2, 2008. Archived from the original on September 4, 2008. Retrieved September 3, 2008.
  285. ^ Chromium Project (March 2011). “ChromiumBrowserVsGoogleChrome”. Retrieved July 10, 2011.
  286. ^ McAllister, Neil (September 11, 2008). “Building Google Chrome: A first look”. InfoWorld. IDG. Archived from the original on September 13, 2008. 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.
  287. ^ “Differences between Google Chrome and Linux distro Chromium”. 2010. Retrieved September 1, 2010.
  288. ^ “Chromium revision log: Changes in revision 271531”. May 20, 2014. Retrieved May 24, 2014.
  289. ^ “Change log for Chromium wiki showing removal of a part that said PDF support were different between Chromium and Google Chrome”. May 20, 2014. Retrieved May 24, 2014.
  290. ^ Garthwaite, Emily. “Google throws PDFium into the open source community”. IT Pro Portal. Retrieved September 11, 2016.
  291. ^ “Developer’s Guide – Google Chrome”. Retrieved February 17, 2014.
  292. ^ “Chrome Web Store”.

External links

160 ms 9.5%
    Scribunto_LuaSandboxCallback::callParserFunction 140 ms 8.3%
    dataWrapper 140 ms 8.3%
    Scribunto_LuaSandboxCallback::find 120 ms 7.1%
    Scribunto_LuaSandboxCallback::match 100 ms 6.0%
    Scribunto_LuaSandboxCallback::getExpandedArgument 100 ms 6.0%
    select_one 80 ms 4.8%
    date 60 ms 3.6%
    citation0 60 ms 3.6%
[others] 480 ms 28.6%

Paula Fonseca