Tag Archives: google chrome

Chrome 24 fixes two dozen bugs. Promising a faster Chrome.

Google’s latest browser update landed today with little fanfare from Mountain View– just a tiny blog post proclaiming a faster, more stable Chrome. Diving into the build’s change notes, however, reveal Flash updates, bug fixes and support for MathML. Not a lot in the way of consumer facing features — though Bookmarks are now searchable, via the Chrome omnibox. Not as fancy as the last release, but we never to scoff at stability and speed. Check it out at the source link below.

The biggest improvement on the user side of things is the speed increase. Google’s own Octane JavaScript test shows that this is the fastest Chrome release yet. When the beta came out in November, the company was touting that Chrome had become 26 percent faster on Octane than it was last year. Now it’s even faster.

On the developer side, Google has made sure the HTML 5 datalist element now supports suggesting a date and time and has also added support for MathML. Datalist allows you to specify a list of suggested dates and times for input elements while MathML lets you write mathematical content in a consistent way. Other additions include experimental support for CSS Custom Filters.

Aside from the usual bug fixes, speed enhancements, a new version of V8 and Webkit, here is what Google listed as being new in Chrome version 24, according to its changelog notes on the previous beta and dev updates (added in chronological order):

  • Bookmarks are now searched by their title while typing into the omnibox with matching bookmarks being shown in the autocomplete suggestions pop-down list. Matching is done by prefix. Example: if there is a bookmark with a title of “Doglettes & Catlettes” typing any of the following into the omnibox will likely present the bookmark as a suggestion:: “dog”, “cat”, “cat dog”, “dog cat”, “dogle”, etc. Typing “ogle” or “lettes” will not match.

That’s right; there was only one new feature mentioned as this appears to be largely a cleanup and stability release. We did see, however, a huge number of notes on what issues have been addressed. Bugs related to Flash, speech input, YouTube, the omnibox, bookmark sync, installing extensions, memory leaks, JavaScript rendering, scrolling, and ones specific to Windows 8 have all been squashed. The full SVN revision loghas more details.

browser-features

On the security side, Chrome 24 coincidentally addresses 24 security holes (11 rated High, 8 marked Medium, and 5 considered Low):

  • [$1000] [162494] High CVE-2012-5145: Use-after-free in SVG layout. Credit to Atte Kettunen of OUSPG.
  • [$4000] [165622] High CVE-2012-5146: Same origin policy bypass with malformed URL. Credit to Erling A Ellingsen and Subodh Iyenger, both of Facebook.
  • [$1000] [165864] High CVE-2012-5147: Use-after-free in DOM handling. Credit to José A. Vázquez.
  • [167122] Medium CVE-2012-5148: Missing filename sanitization in hyphenation support. Credit to Google Chrome Security Team (Justin Schuh).
  • [166795] High CVE-2012-5149: Integer overflow in audio IPC handling. Credit to Google Chrome Security Team (Chris Evans).
  • [165601] High CVE-2012-5150: Use-after-free when seeking video. Credit to Google Chrome Security Team (Inferno).
  • [165538] High CVE-2012-5151: Integer overflow in PDF JavaScript. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [165430] Medium CVE-2012-5152: Out-of-bounds read when seeking video. Credit to Google Chrome Security Team (Inferno).
  • [164565] High CVE-2012-5153: Out-of-bounds stack access in v8. Credit to Andreas Rossberg of the Chromium development community.
  • [Windows only] [164490] Low CVE-2012-5154: Integer overflow in shared memory allocation. Credit to Google Chrome Security Team (Chris Evans).
  • [Mac only] [163208] Medium CVE-2012-5155: Missing Mac sandbox for worker processes. Credit to Google Chrome Security Team (Julien Tinnes).
  • [162778] High CVE-2012-5156: Use-after-free in PDF fields. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [162776] [162156] Medium CVE-2012-5157: Out-of-bounds reads in PDF image handling. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [162153] High CVE-2013-0828: Bad cast in PDF root handling. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [162114] High CVE-2013-0829: Corruption of database metadata leading to incorrect file access. Credit to Google Chrome Security Team (Jüri Aedla).
  • [Windows only] [162066] Low CVE-2013-0830: Missing NUL termination in IPC. Credit to Google Chrome Security Team (Justin Schuh).
  • [161836] Low CVE-2013-0831: Possible path traversal from extension process. Credit to Google Chrome Security Team (Tom Sepez).
  • [160380] Medium CVE-2013-0832: Use-after-free with printing. Credit to Google Chrome Security Team (Cris Neckar).
  • [154485] Medium CVE-2013-0833: Out-of-bounds read with printing. Credit to Google Chrome Security Team (Cris Neckar).
  • [154283] Medium CVE-2013-0834: Out-of-bounds read with glyph handling. Credit to Google Chrome Security Team (Cris Neckar).
  • [152921] Low CVE-2013-0835: Browser crash with geolocation. Credit to Arthur Gerkis.
  • [150545] High CVE-2013-0836: Crash in v8 garbage collection. Credit to Google Chrome Security Team (Cris Neckar).
  • [145363] Medium CVE-2013-0837: Crash in extension tab handling. Credit to Tom Nielsen.
  • [Linux only] [143859] Low CVE-2013-0838: Tighten permissions on shared memory segments. Credit to Google Chrome Security Team (Chris Palmer).

Google thus spent a total of $6,000 in bug bounties this release. These issues alone should be enough to get you to upgrade to Chrome 24

Capture

Aura: Bleeding Edge of Chrome OS. Brief Post.

google chrome os aura

Our Samsung Series 5 Chromebook hasn’t gotten much love recently, but Google just pushed out an update through its developer channel, called “Aura.” We downloaded and tested the new update, and were surprised how suddenly… familiar it felt.

To put it simply, the changes in Aura are clearly designed to make the Chromebook feel like a laptop rather than a browser with a keyboard. There’s actually a desktop, with a background and everything. There are icons at the bottom on the left side, and a Quick Launch-style menu on the right side — it looks just like the Windows 7 taskbar. The right-most icon in the list opens a page of bookmarks that looks a whole lot like the Launch Pad feature in OS X Lion, except that instead of apps it’s shortcuts to websites. Aura feels like a mix between Mac OS and Windows 7, and it’s clear that’s where Google’s trying to take its operating system.

launchpad_560

Our favorite of the bookmarks is “Scratchpad,” which pops up a tiny floating window that lets you take quick notes — kind of a lighter Simplenote app. Scratchpad hooks into Google Docs, too, so you get a folder called “Scratchpad” with all your notes inside. It’s the closest thing to a non-Chrome app we’ve seen yet on Chrome OS, and it’s a pretty clever tool.

Everything still happens in Chrome, obviously, but fortunately you can now have multiple windows open at once — that makes multitasking a whole lot easier. As you drag windows around, they’ll snap to the display’s edges, so you can quickly move a window over and have it automatically fill half the screen. It works just like Aero Snaps in Windows 7, and by itself makes the Chromebook a lot more usable than just having one immovable window with infinite tabs. The whole OS felt faster than ever, too, enough to make us jealous that Chrome’s not always so responsive.

The basic concept of a Chromebook hasn’t changed with the new update, and we’re still more intrigued with what Google Drive could mean for Chrome OS anyway. Google’s clearly trying to make the Chromebook feel a little more like a laptop, with a user interface and design that should be a lot more familiar to people who use Windows or Mac OS, and like to open apps other than a full-screen browser from time to time. Google’s clearly still committed to the OS, and we’ll be watching to see where it goes next.

The newest update to Google’s Chrome OS is bringing the browser-based operating system a lot closer to a traditional windowing environment. Development channel (the least stable build) version 19.0.1048.17 adds Google’s hardware-accelerated Aura UI and window manager, bringing a desktop, overlapping windows, a Windows-style taskbar, and a Launchpad-esque app launcher to the platform.

According to the project’s wiki, the goal of Aura is to use hardware acceleration to achieve more computationally intensive tasks like large-scale animated transitions and effects as well as to provide the basis for a flexible windowing system. Aside from Aura, other new features in the latest dev channel release include support for new file types (tar, gz, and bzip2), updates to the local audio and video player, and new modes for multiple monitor handling. Unfortunately, early-adopting Cr-48 owners are out of luck — the build of Chrome OS in question is only for Acer AC700 and Samsung Series 5 Chromebooks.

Add A Refresh/Stop Button To The Address Bar In Chrome For iPhone

Everyone appears to be absolutely in love with the Chrome app for iOS. The first impression of the new iPhone web browser might be that it is perfect, and has got all the features anyone can possibly want. However, that is not the case. Although Chrome is better than Safari in quite a few areas, there are still things that could have been better in Google’s official browser app for iPhone and iPad. If you don’t believe that, and happen to think that nothing can be improved in Chrome, take a look at our post discussing some of the best Chrome-related Cydia tweaks available in the jailbreak store. The Cydia developer community isn’t satisfied with the Chrome app just yet, and the latest tweak released for the enhancement of the browser is named EasyRefresh for Chrome. If you have ever used the Chrome app on your iPhone, you are sure to have noticed that if you want to refresh any page, you have to go to the app’s options menu and tap the button from there. EasyRefresh solves this problem by adding a new refresh button to the address bar, just the way it works in Safari!

Chrome iOS Default EasyRefresh for Chrome Cydia EasyRefresh for Chrome

Before installing the tweak, go to the Chrome app and take a look at the address bar. It has got nothing except the URL of the page you are currently on. The options menu features the refresh/ stop button at the top of the list. EasyRefresh for Chrome will not disturb this refresh button, it will just copy it to the address bar. The tweak can be downloaded from the BigBoss repo of the Cydia store, where (quite expectedly) it is available as a free download. The whole package is just 13kB in size, and will finish installing in the blink of an eye. After downloading EasyRefresh, launch Chrome again. It is better if you kill the app from the App Switcher tray before re-launching it, but that is not a necessary step. Once the app is up and running, take a look at the address bar, and you will see the newly added refresh button there. While a page is loading, the button will be displayed as a cross icon that can be used to stop loading a page at any time. Other than that, the button is there to let you refresh the page.

Of course, EasyRefresh is just one of the ways you can have an alternative to the stock refresh method in Chrome. The Chromizer tweak (covered in detail in our list post linked in the intro) adds the pull to refresh functionality to Chrome. However, if you are a fan of the address bar refresh button, EasyRefresh is the tweak you need.