Google increases the energy efficiency of the Chrome browser in a number of scenarios up to 25%

Recently, Chrome updates have passed quite unnoticed due to the fact that most of the changes concerned the introduction of new APIs for developers, especially for game developers . That is why the latest entries in the official Google blogs were relatively succinct. The new version of Google Chrome 23, which has now moved from the Beta update channel to the Stable update channel, not only fixes “under the hood” (although without them), but also a number of improvements that can be seen in the usual work with the browser: video decoding now occurs using hardware acceleration by means of GPU, which will play a positive role on the duration of work of portable computers, as well as added a clear permissions manager for each site.

Hardware accelerated video decoding

The guys from Google did a great job in this direction, given the fact that the standard for Chrome was decoding video via ffmpeg, which worked without any problems. But Google got confused and began to screw up the possibilities of GpuVideoDecodeAccelerator, despite the fact that Chrome does not work on one system. The result of the hard work of adaptation was that, according to Google, the consumption of processor resources when watching videos was reduced by 25%. Google tested this video on a Lenovo T400 under Windows 7. Naturally, power consumption on different hardware and OS can vary greatly, but the innovation itself is very useful.

Site Permissions Manager

Google finally moved a convenient permissions manager for sites from Opera, which kept me from switching to Chrome for a long time, but two years later this functionality was added, and it’s cool. Now you can without any tweaks to set specific settings for each site in a convenient window, and not to go into the settings and suffer with tedious prescribing exceptions. Do not want pictures on a particular site? No problem, two clicks of the mouse, and the problem is solved. It is the same with JavaScript scripts, plug-ins, cookies (it was before, but not so convenient), access to the microphone, location, etc. Just click on the page icon in the omnibox, and the manager is ready for battle. It looks like this:





')

I want the same thing in the Android Open Source Project , and I do not want to wait for JVA of the year = D

Under the hood in one line

• Added option Do Not Track . Now you can tell websites that you don't want targeted content. Major European and American sites have learned to understand this title, but there is no certainty about other sites. The option is disabled by default, but it can be enabled in advanced settings.
• HTML5 subtitle support implemented
• Implemented support for input type = time
• Adobe Flash 11.5 . Despite the fact that Flash Player switched to a new iteration of branch 11. *, this did not bring much new tasty buns. Most bug fixes
• Fix vulnerabilities . This time, Chrome did without critical vulnerabilities, but 6 with a high degree were discovered and successfully fixed. Of these six, four found the participants of the project Chromium not from Google, for which they received $ 4000. Vulnerability details are traditionally kept secret until most users upgrade to Chrome 23.