User:Helpfoss/Comparison of web browsers

The following tables compare general and technical information for a number of web browsers.

Operating system support
Browsers are compiled to run on certain operating systems, without emulation. For a given browser/OS combination, browser support status can be one of six possibilities: This list is not exhaustive, but rather reflects the most common OSs today (e.g. Netscape Navigator was also developed for OS/2 at a time when Mac OS X did not exist) but does not include the growing appliance segment (for example, the Opera web browser has gained a leading role for use in mobile phones, smartphones, the Nintendo DS and Wii, and Personal Digital Assistants, and is also used in Interactive televisions). Both the web browser and OS means most recent version, example: Windows 7 with Internet Explorer 8.
 * No means that it does not exist or was never released.
 * Partial means that the browser works, but lacks important functionality or is very unstable compared to versions for other OSs, that is to say it has roughly alpha or pre-alpha quality, and it is still being developed.
 * Beta means that a version of the browser is fully functional and has been released, but is still in development, e.g., for stability.
 * Yes means that the browser has been officially released in a fully functional, stable version.
 * Dropped means that the latest stable version of the browser does not work on the operating system, although an older version is available that does. The number in parentheses is the last known stable version which was officially released for that OS.
 * Included means that the browser comes pre-packaged as part of or has been integrated into the operating system.

Acid Scores
'The Acide Scores are depend entirely on the Layout Engine-Version, and not for the browser...

The Acid tests are online test suites to determine aspects of standards compliance, to expose web page rendering flaws, and to rate the performance of browsers. Upon each test's release, they are designed so that no existing browser can pass without further development. In order for a browser to pass any Acid test, the latest public release of the browser (not an alpha, beta, release candidate, or other version under development or testing procedures) must meet the requirements shown below. In addition, the browser should be tested upon completion of installation, with no add-ons installed (some browsers make this easy by providing a "safe mode" option) and all the factory settings (no options have been changed from their defaults).

Acid1:
 * Final rendering looks exactly like the rendering provided by the Acid tests website.
 * Text can be highlighted and radio buttons can be selected.

Acid2:
 * Final rendering looks exactly like the rendering provided by the Acid tests website.
 * Smiley's nose turns blue when hovered over.

Acid3:
 * Final score of 100/100.
 * No error messages on final rendering.
 * Render-in-progress loads smoothly (no pausing).
 * Final rendering looks exactly like the rendering provided by the Acid tests website.

HTML5 support
The specifications for HTML5 are still under development, but many current browsers already support many of the new features in the draft specifications. An HTML5 test suite is also under development that, while it does not test all of the new features nor the functionality of those it does detect, rates browsers' support. New tests are expected to be added to the suite as time goes by.

Web technology support
Information about what web standards, and technologies the browsers support, except for JavaScript. External links lead to information about support in future versions of the browsers or extensions that provide such functionality.

Mobile Web technology support
Information about what web standards, and technologies the browsers support, except for JavaScript. External links lead to information about support in future versions of the browsers or extensions that provide such functionality.

JavaScript support
Information about what JavaScript technologies the browsers support. Note that although XPath is used by XSLT, it is only considered here if it can be accessed using JavaScript. External links lead to information about support in future versions of the browsers or extensions that provide such functionality.


 * See what parts of DOM your browser supports.


 * HTTP
 * E-mail
 * FTP
 * NNTP (Usenet)
 * SSL
 * EV
 * IRC
 * Gopher
 * IDN
 * data:URI
 * BitTorrent
 * IPv6
 * Proxy possibilities