GoogleRelease web-browser Chrome 28 with the increase of minimum requirements for the Linux-based system

The browser is built on the code base open source project Chromium and characterized by using the logos of Google, built-in Flash and PDF, the presence of notification in the event of failure, the system automatically updates and transmission when looking RLZ-parameters.

The main changes:

– Dropped support for older releases Linux-distributions, including Chrome 28 now can not be used in RHEL 6 and Debian 6 (Squeeze). Minimum requirements for distributions raised to Ubuntu 12.04 +, Debian 7 +, OpenSuSE 12.2 + and Fedora Linux 17 +. Improving the system requirements due to the termination of support in Chrome and Chromium older versions of the library GTK +, younger version 2.24;

– In the browser engine Blink (a fork of WebKit) involved a new multi-threaded parser HTML. The new parser is notable removal stage parsing HTML from the main thread JavaScript and speed up page load due to pipelining content (processing the next block starts before the end of the previous treatment). Compared with the previously used parser managed to increase the speed of loading DOM-content of 10% and a 40% reduction in the maximum time a suspension of processing during the parsing;

– In V8 engine added additional optimizations to speed up the code JavaScript. In particular, the changes have allowed more than two-fold increase in the speed of the applications that use Asm.js, promoted by the Mozilla developers of low-level subset of the JavaScript language with strong typing. A subset of JavaScript, proposed in Asm.js, fully compatible with conventional JavaScript and can run in any browser, as all the additional information is defined in the form of annotations;

– In addition to SPDY/3.1 implemented experimental support for the preliminary version of the protocol SPDY / 4;

– HTML-header Content Security Policy rid of the prefix “X-WebKit-” and is now treated as a “Content-Security-Policy”. Support options with the prefix (“X-WebKit-CS”) until saved but will be discontinued in future releases. Technology Content Security Policy efforts to integrate into web-browsers special HTTP-heading for the protection of the organization of cross-site scripting (XSS) and substituting the page “IFRAME / JavaScript src” blocks. Using the title on web-master can explicitly specify which of the scripts can be performed for a given domain, for example, you can allow only the performance of local JavaScript-file and block the execution of JavaScript-blocks defined directly in the HTML document or hosted on an external site;

– Deprecated HTML API (call createHTMLNotification) to display the notification of the extensions to the browser Chrome. To display the notifications should use the new Rich Notifications Chrome API, a remarkable ability to create interactive notifications, interacting with the user;

– Support for CSS-pseudo “@ supports”, allowing to test the support for specific properties and values ​​of CSS. If support is requested property is absent, the developer an opportunity to transparently use the program fallback;

– Support for CSS-pseudo “: unresolved” to define a style using another browser is not registered in the entry specified by Custom Element.