Thursday, April 18, 2013

Chrome Beta for Android Update

Chrome Beta for Android has been updated to 27.0.1453.60 for ARM and x86. This release contains a few new fixes including:
  • 226691: Graphical corruption and blank tabs in tab switcher mode 
  • 222805: Most Visited section thumbnails are misaligned in landscape mode for RTL languages
  • 228883: Search is still performed via Google when re-submitting omnibox query after switching search engine
  • Flicker while opening new tabs
  • Fixes for some frequently occurring crashes
  • chrome://history sometimes show duplicate items
Known Issues:
  • Opening tabs is sometimes slow
  • Pages may flicker sometimes, especially during navigation 
  • Typed character gets deleted sometimes on password fields
A partial list of changes in this build is available in the SVN revision log. If you find a new issue, please let us know by filing a bug. More information about Chrome for Android is available on the Chrome site.

Jason Kersey
Google Chrome


Alen said...

Great fixes!!!

John Farrell said...

Excellent !

developer android

No Blog Name said...

Still now fullscreen for tablets.

drbaltazar said...

Google need to optimise cell tower switching (or help T-Mobile at least)because right now it is an issue (especially on edge)it take too much phone resource.also that isn't optimised for where you the switching might be sent 2000 mile away .bufferbloat is another issue .1000 +millisecond is the norm .please Google send your road warrior on the road with programmer you all see what I mean very quickly.also when tower switching occur most program act up be it from Google or other.please look into this .this is a big issue.lastly disable all unnecessary when on edge network (like how much time left etc.(its useless on edge)

poumpoumk said...

Full screen on tablet please !

On iOS, with "on Save to Home Screen" bookmarked web sites, it just launches Safari in a light version with no "browser chrome". I think that a lot of people would love that on Android (a way better than all the window.scrollTo() tricks).