Today Google has pushed a quick update out to their popular Google Chrome browser for Android smartphones and tablets. While the browser still isn’t available for everyone in the world of Android it is slowly making great progress, and even will come pre-installed on upcoming Motorola phones. Check out the new details below.

Google’s been rather quiet on Chrome updates in the past but this time around they gave us a decent little list of changes. The new version is listed as Chrome M18.1 and has tons of stability and overall security improvements. Apparently Chrome’s sandbox feature has been seriously overhauled on this update, although they don’t mention that but the folks from Android Police caught notice. Here’s the quick change-log:

-Location preference now integrated to system level Google apps location setting.
-Youtube videos controls now work in full screen mode; videos continue playing after a screen lock/unlock
-Fixes to make third-party IMEs work better with Chrome

You’ll probably notice the YouTube video controls now work great in full screen mode, something that was a disaster before this update. Personally I just head right to the YouTube app myself when prompted in Jelly Bean — but everyone is different I suppose. Then it will pause/resume with ease if you put your phone to sleep. Before we’d have issues where it would freeze and you’d need to start over on your video.

Last but not least they mention some additional support for all those third party IMEs to now work better with Chrome for Android. This means many keyboards like SwiftKey 3 that might have had a few issues should now work with ease. There is also some very very minor UI changes as well as options such as “report an issue” that have been removed from the settings menu. For those who love Chrome and want the latest and fastest version for Android hit the link below and get it today.

Google Chrome for Android

2 COMMENTS

  1. I dunno. For me, the update screwed up something in SwiftKey’s workaround mode that causes the cursor to jump around when backspacing. Maybe SwiftKey just needs to remove the workaround now?

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.