Google Chrome

Features

Google Chrome aims to be secure, fast, simple and stable. There are extensive differences from its peers in Chrome's minimalistic user interface, which is atypical of modern web browsers. For example, Chrome does not render RSS feeds. 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. Many of Chrome's unique features had been previously announced by other browser developers, but Google was the first to implement and publicly release them.For example, its most prominent graphical user interface (GUI) innovation, the merging of the address bar and search bar (the Omnibox), was first announced by Mozilla in May 2008 as a planned feature for Firefox.Web standards support

Chrome has currently quite good support for JavaScript/ECMAScript according to Ecma International's ECMAScript standards conformance Test 262 (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 21.0.1180 scored 17/11570, the beta version 22.0.1215.1 scored 16/11570, and the dev version 23.0.1240.0 scored 8/11570. For comparison, Firefox 15 scored 172/11750 while Internet Explorer 9 has a score of 600+.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.

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

On the HTML5 test (April, 2012 – version 3.0) Chrome version 21.0.1180.83 scored 447 out of 500, with 13 bonus points.

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

Chrome will typically allocate each tab to fit into its own process to "prevent malware from installing itself" and prevent what happens in one tab from affecting what happens in another; however, the actual process-allocation model is more complex. Following theprinciple 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. TheSandbox Team is said to have "taken this existing process boundary and made it into a jail"; for example, malicious software running in one tab is supposed to be unable to sniff credit card numbers entered in another tab, interact with mouse inputs, or tell Windows to "run an executable on start-up" and it will be terminated when the tab is closed. This enforces a simple computer security model whereby there are two levels of multilevel security (user and sandbox) and the sandbox can only respond to communication requests initiated by the user. On Linux sandboxing uses the seccomp mode.

Click here To DOWNLOAD