Google Chrome, a browser built on the Blink layout engine that aims to be minimalistic and versatile at the same time, has been upgraded to version 37.0.2041.4 and comes with a large number of changes.
The Google developers have launched a new version of their Chrome browser, but this is just the development branch. It's possible that some of the features integrated in this version of the browser will never make it to Beta and Stable.
Google Chrome Dev is the place where the developers implement new features and where the majority of fixes are added. There have been very few times when the Dev release wasn’t large, and this is not one of those times.
According to the changelog, pause and buffer are now suppressed for local resources, an input data parser has been added for Mojo message validation tests, a loop in GN has been fixed, a trivial end-to-end (in-process) test of Mojo shell has been added, libxslt has been added to the GN build, the LLVMpipe GL driver is now loaded in the Chromoting desktop session, the same vk non-overscroll solution is now used for both the login and lock screens, and a bug that occurred on search has been fixed.
Also, pressing the Enter key no longer crashes the overview mode without a selection, an extension has been added to override the bubble and warning box for proxy extensions, a docked panel is now visible on all KDE desktops, libudev1:i386 is now provided for Ubuntu 14.04, a browser-global GCMDriver has been added, the V8 engine has been updated to a new version, the recovery from SSL errors is now handled better, TextEvent support has been implemented for Linux, and much more.
The Google Chrome developers only provide two kinds of binary files, deb and rpm, and no source. If you are not using a Linux distribution capable of reading this type of files, you will have to wait until it hits your repositories.
Also, keep in mind that if you intend to use this browser on the Linux platform, the Java elements will not work. In order to access Java components on a website you will need to downgrade.
Usually, a complete list of changes can be found on the official website.
Remember that this is a development version and it should NOT be installed on production machines. It is intended for testing purposes only.