<http://schema.org/articleBody>
"Google today released Chrome version 34 for Windows, Mac, and Linux. The new version includes support for responsive images, an unprefixed version of the Web Audio API, and importing supervised users. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome.\r\n\r\nFirst off, Google is introducing the &amp;quot;srcset&amp;quot; attribute to let Web developers provide multiple resources in varying resolutions for a single image, in the hopes of speeding up page load times, reducing wasted bandwidth, and ending improperly formatted content. In short, support for responsive images means the browser picks the resource that matches the device's capabilities, whether it\u2019s a desktop, laptop, tablet, phone, or a TV.\r\n\r\nNext, the new browser release comes with an unprefixed version of the Web Audio API, to bring Chrome's implementation of Web Audio in alignment with the W3C draft specification. Google is asking developers to switch to the unprefixed versions as the prefixed versions have been deprecated and will be removed completely in a future release.\r\n\r\nHere's the Chrome 34 changelog provided by Google:\r\n\r\nResponsive Images and Unprefixed Web Audio.\r\nImport supervised users onto new computers.\r\nA number of new apps/extension APIs.\r\nA different look for Win8 Metro mode.\r\nLots of under the hood changes for stability and performance.\r\n\r\n\r\nThe second point is worth expanding on: you can now import supervised users, which were first added as a beta feature Chrome 32. Imported supervised users come with all their permissions, which will automatically sync across devices.\r\n\r\n\r\n\r\nTo import a supervised user, click the Chrome menu on the browser toolbar, select Settings, click &amp;quot;Add new user&amp;quot; in the Users section, click &amp;quot;Import an existing supervised user,&amp;quot; select the user in question, and click &amp;quot;Import supervised user.&amp;quot; As we noted for the beta, Google should probably cut down a few of those steps.\r\n\r\nAs in previous releases, Google also included the usual bug fixes, stability improvements, and so on in Chrome version 34.0.1847.116. For more details, you can check out the full SVN revision log.\r\n\r\nLast but certainly not least, Chrome 34 also addresses 31 security issues, of which Google chose to highlight the following:\r\n\r\n[$5000][354123] High CVE-2014-1716: UXSS in V8. Credit to Anonymous.\r\n[$5000][353004] High CVE-2014-1717: OOB access in V8. Credit to Anonymous.\r\n[$3000][348332] High CVE-2014-1718: Integer overflow in compositor. Credit to Aaron Staple.\r\n[$3000][343661] High CVE-2014-1719: Use-after-free in web workers. Credit to Collin Payne.\r\n[$2000][356095] High CVE-2014-1720: Use-after-free in DOM. Credit to cloudfuzzer.\r\n[$2000][350434] High CVE-2014-1721: Memory corruption in V8. Credit to Christian Holler.\r\n[$2000][330626] High CVE-2014-1722: Use-after-free in rendering. Credit to miaubiz.\r\n[$1500][337746] High CVE-2014-1723: Url confusion with RTL characters. Credit to George McBay.\r\n[$1000][327295] High CVE-2014-1724: Use-after-free in speech. Credit to Atte Kettunen of OUSPG.\r\n[$3000][357332] Medium CVE-2014-1725: OOB read with window property. Credit to Anonymous\r\n[$1000][346135] Medium CVE-2014-1726: Local cross-origin bypass. Credit to Jann Horn.\r\n[$1000][342735] Medium CVE-2014-1727: Use-after-free in forms. Credit to Khalil Zhani.\r\n\r\n\r\nGoogle thus spent at least $29,500 in bug bounties this release. These fixes alone should push Chrome users to upgrade as soon as possible."^^<http://www.w3.org/2001/XMLSchema#string>
<http://thenextweb.com/google/2014/04/08/chrome-34-launches-support-responsive-images-unprefixed-web-audio-importing-supervised-users/>