What's in the latest Chrome update? Google this week boosted Chrome to version 71, the last refresh of 2018 and one that includes punitive measures against sites spewing what the search giant.
Google this week boosted Chrome to version 71, the last refresh of 2018 and one that includes punitive measures against sites spewing what the search giant described as 'abusive experiences.' Chrome 71 also patched 43 security vulnerabilities reported by outside researchers, who were paid $59,000 in finders' fees. Related: Chrome updates in the background, so users can typically just relaunch the browser to install the latest. To manually update, select 'About Google Chrome' from the Help menu under the vertical ellipsis at the upper right; the resulting tab either shows the browser has been updated or displays the download process before presenting a 'Relaunch' button.
![Latest chrome browser version for mac Latest chrome browser version for mac](/uploads/1/2/5/4/125447318/237354796.jpg)
New-to-Chrome users can download it from for Windows, macOS or Linux. The Mountain View, Calif. Company updates Chrome every six to seven weeks. It last upgraded the browser on Oct. Slapping some sites with total ad embargo A month ago, Google ran an, telling Chrome users, 'Starting in December 2018, Chrome 71 will remove all ads on the small number of sites with persistent abusive experiences.'
(Google.) Removing all ads could, of course, easily put an advertising-dependent website on the poor farm. That's the point. Through Chrome - which dominates the Web - Google has been shaping online to its taste, often using the browser as a bludgeon to punish sites or practices it feels are hostile to customers or noxious to itself. Auto-play policies, meet Web Audio the process of synchronizing the already-in-place auto-play rules in Chrome - which generally, though not always, block ads from blaring sound from a PC's speakers as soon as a site renders - with the Web Audio API (application programming interface). According to Google, the sync has not yet been enabled, but is tucked behind one of the option flags which can be set in the UI at chrome://flags. At its most basic, the API can be used by site and app developers to add audio to their creations.
Currently, only Chrome - via the, which feeds code to the production browser - supports Web Audio. Chrome, like rival browsers, has been hammering against sites' auto-playing audio because of user complaints that the blaring is annoying at best. Most of the auto-play instances have been initiated by advertisements, another reason people have become increasing fed up with the Web and its underpinnings. The move to make Web Audio follow Chrome's standard auto-play practices can be seen as simply an expansion of a long-running battle. Third-party code blocking delayed again for enterprise users Google also patched 43 vulnerabilities in version 71, including 13 marked 'High,' the second-most serious ranking in its four-step system. The company cut checks totaling $59,000 to researchers who reported 28 of the bugs.
In the enterprise edition of Chrome, a well-publicized decision this summer that the browser would soon block all third-party code injections has been put on indefinite hold. Billed as a stance on security and stability, the anti-injection mandate was, Google said in October, to go into effect by default with Chrome 71.
'Due to an issue with anti-virus file scanning, we're delaying this change until we have a solution that better covers customers' needs,' Google said in the. This move has been postponed more than once; it was to roll out for enterprise customers in Chrome 68 (July), then in Chrome 69 (September). Chrome's next upgrade, version 72, will reach users on or about Jan.
![For For](/uploads/1/2/5/4/125447318/897849901.png)
. Linux. How do I choose which channel to use? The release channels for chrome range from the most stable and tested (Stable channel) to completely untested and likely least stable (Canary channel). On Windows, Android, and Linux, you can run all channels alongside all others, as they do not share profiles with one another.
On Mac, you can run the Canary channel builds alongside any other channel, as they do not share profiles with other channels. This allows you to play with our latest code, while still keeping a tested version of Chrome around. Stable channel: This channel has gotten the full testing and blessing of the Chrome test team, and is the best bet to avoid crashes and other issues.
It's updated roughly every two-three weeks for minor releases, and every 6 weeks for major releases. Beta channel: If you are interested in seeing what's next, with minimal risk, Beta channel is the place to be. It's updated every week roughly, with major updates coming every six weeks, more than a month before the Stable channel will get them. Dev channel: Want to see what's happening quickly, then you want the Dev channel. The Dev channel gets updated once or twice weekly, and it shows what we're working on right now.
There's no lag between major versions, whatever code we've got, you will get. While this build does get tested, it is still subject to bugs, as we want people to see what's new as soon as possible. Canary build: Canary builds are the bleeding edge.
Released daily, this build has not been tested or used, it's released as soon as it's built. Other builds: If you're absolutely crazy, you can download the latest working (and that's a very loose definition of working) build from. You can also look for a more specific recent build by going to, looking at the number near the top under 'LKGR', and then going to and downloading the corresponding build. Note: Early access releases (Canary builds and Dev and Beta channels) will be only partly translated into languages other than English. Text related to new features may not get translated into all languages until the feature is released in the Stable channel. What should I do before I change my channel?
Back up your data! Before you switch, you should make a backup of your profile (bookmarks, most visited pages, history, cookies, etc). If you ever want to switch back to a more stable channel, your updated profile data might not be compatible with the older version. Make a copy of the User Data Default directory (for example, copy it to 'Default Backup' in the same location). Reporting Dev channel and Canary build problems Remember, Dev channel browsers and Canary builds may still crash frequently. Before reporting bugs, consult the following pages:. See before reporting problems in Mac or Linux Dev channel builds If after reading the above, you think you have a real bug, file it - Going back to a more stable channel.
If you decide to switch from Dev to Beta or from Beta to Stable, the new channel will be on an earlier version of Google Chrome. You won't get automatic updates on that channel until it reaches a version later than what you're already running. You can uninstall Google Chrome and re-install from to go back to an earlier version.
If you re-install an older version, you might find that your profile is not compatible (because the data formats changed in the newer version you had been running). You'll have to delete your profile data. Delete the User Data Default folder (see the Before You Change Channels section above for the location). If you made a back up of your Default directory, you can then rename it to Default so that you at least restore some of your previous bookmarks, most visited pages, etc. If the installer fails when you attempt to install an older version with a message indicating that your computer already has a more recent version of Chrome or Chrome Frame, you must also uninstall Chrome Frame. After doing so, the newer version of Chrome should install without difficulty.