Recommended Posts

Dev Channel Update

The Dev channel has been updated to 22.0.1201.0 for Windows, Mac, Linux and Chrome Frame. This build has an update version of V8 (3.12.9.0) along with the following changes in the svn log.

Please note, on Mac we now require 10.6 or higher, and this release will not be available if you are on 10.5 or lower. You can find out how to change to the Dev channel, or any channel, on chromium.org. If you find a new issue with this release, please shoot us a bug report.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

Link to comment
https://www.neowin.net/forum/topic/1090147-google-chrome-220xxxxyy/
Share on other sites

Dev Channel Update

The Dev channel has been updated to 22.0.1207.1 for Windows, Mac, Linux and Chrome Frame. This release contains the following changes:

All Platforms

Windows

  • Fix new installation suffix in [r146217]. Users who installed dev-channel from scratch (i.e. not updating from stable/beta) between July 9th and July 16th might have two Google Chromes show up in ?Default Programs? (uninstalling/reinstalling will fix this).

The full list of changes is available in the svn revision log. You can find out how to change to the Dev channel, or any channel, on chromium.org. If you find a new issue with this release, please shoot us a bug report.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

Dev Channel Update

The Dev channel has been updated to 22.0.1215.0 for Windows, Mac, Linux and Chrome Frame. This build has an update version of V8 (3.12.14.0) along with the following changes in the svn log.

The Pepper Flash Player Plugin has been turned on by default on Mac OSX.

You can find out how to change to the Dev channel, or any channel, on chromium.org. If you find a new issue with this release, please shoot us a bug report.

Anthony Laforge

Google Chrome

Source: Google Chrome Releases blog

Note: At the moment the update push for the Windows build has been halted due to a bug. Workaround: Install it from https://www.google.com/chrome/eula.html?extra=devchannel.

Dev Channel Update

The Dev channel has been updated to 22.0.1221.0 for Windows and Mac. This update has an updated version of V8 (3.12.16.0) along with other improvements. A complete log of what changed can be found in the svn revision log. Instructions and download links for our different release channels are available on the Chromium wiki. If you find what you think is a new bug, please file it in our issue tracker.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

hey meph, can you start putting these updates in the Meet Chrome Next thread? it was created recently to help keep things centralized for the chrome releases similar to the meet firefox next thread, and this way a new thread doesn't need to be created every time the main version number jumps

hey meph, can you start putting these updates in the Meet Chrome Next thread? it was created recently to help keep things centralized for the chrome releases similar to the meet firefox next thread, and this way a new thread doesn't need to be created every time the main version number jumps

Sure thing.

This topic is now closed to further replies.
  • Posts

    • Google are hyprocrites for signing this. They have been pulling the same dirty tactics as Microsoft, only they do it on Android and ChromeOS.
    • In some countries the law has forced Microsoft to display a menu on a fresh install of Windows which asks which web browser you want and it will install that browser. This doesn't add any bloat to Windows. It simply an additional step when setting up a new PC.
    • Chrome is also a first party browser on Android and ChromeOS. And on those systems, Google is pulling the same dirty tactics as Microsoft does on Windows.
    • Unofficial script lets you install unreleased Windows 11 features without Microsoft Account by Sayan Sen Microsoft has been steadily evolving the Windows Insider Program over the years, introducing new channels and testing paths that allow enthusiasts to experience upcoming and yet-to-be-released Windows features (some interesting hidden ones too) before they reach the public. However, one long-standing requirement has remained largely unchanged as users are generally expected to enroll in the Program and with a Microsoft account. That's where a third-party tool called "OfflineInsiderEnroll" can help. OfflineInsiderEnroll is said to be a lightweight script that enables access to Windows Insider Program builds on systems that are not signed in with a Microsoft account. Essentially the tool configures the necessary Insider settings locally and hence allows users to select and switch between available preview channels while continuing to receive builds through the normal Windows Update channel. If you are wondering how it manages to do so, it is made possible by a Registry value known as TestFlags. When configured to"0x20", Windows stops communicating with Microsoft's online Insider enrollment services thus preventing locally configured Insider settings from being overwritten. This allows the script to apply its own channel configuration directly through the Registry as Windows Update does not verify whether a device has been officially enrolled in the Insider Program or not. Previously the utility has had already supported the traditional Insider branches including Dev, Beta, and Release Preview. However following Microsoft’s recent restructuring of its preview channels, the script has now been updated. The latest OfflineInsiderEnroll version, 2.6.6, adds support for the newly introduced Insider channel lineup. As such, users can now choose from several Experimental channels in addition to Beta and Release Preview options. The update also retains tools for refreshing the Insider cache, resetting Insider settings, and completely stopping Insider enrollment when needed. Keep in mind though that will need elevated privileges when running the script (run as Admin). You can get the latest version of OfflineInsiderEnroll from this page on its official GitHub repo.
    • The "Classic" Outlook has done that for a few years as well. The option to even change that is really hidden away too... It really shouldn't be hard to respect user defaults. Sadly we are the product now, not Outlook. To change in the Classic Outlook: File > Options > Advanced > change "Open hyperlinks from Outlook in"
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!