Google Chrome 139 is out: here are the major changes
Google released a new version of its Chrome web browser for desktop operating systems and Android this week. Chrome 139 is a security and feature update, but it also changes the system requirements on Android.
Desktop users can download and install the update via Menu > Help > About Google Chrome. If you are on Windows, you may also run winget upgrade google.chrome.exe to install the latest version.
Chrome 139: the security update
Google mentions on the Chrome Releases Blog that it fixed 12 unique security issues in Chrome 139. It lists eight security issues publicly only, which have a severity rating of either medium or low.
The company makes no mention of exploits in the wild, which means that it is not aware of any targeted attacks.
Chrome 139: the new features and changes
Google introduces an AI Mode for search recommendations in Chrome 139. You may find a new section "Explore in AI Mode" when you click on the address bar or type something. This section complements the suggestions that Google Chrome displays, e.g., if bookmarks match what you type.
The feature is rolled out over time. Means: it make take days, weeks or even longer before you may see the new section.
Enterprise admins may control the feature with the policy AIModeSettings.
Other Changes in Chrome 139:
- Google Chrome 139 does not support Android Oreo or Android Pie anymore. The operating systems launched in 2017 and 2018 respectively.
- Google Chrome 139 does not support macOS 11.
- Chrome 139 on Android contacts Google servers when Android APK files are downloaded to "get a verdict about their safety". If Google determines that an APK is dangerous, it will show a warning and block the download. Users may bypass the warning to proceed with the download. The checks are performed if Standard Protection or Enhanced Protection are enabled in Google Safe Browsing.
- The Passwords and other sign-in data selection in Delete browsing data is removed. Users are redirected to the Google Password Manager instead, as it offers "better manage and delete passwords and passkeys" capabilities".
- Google removed the startup flags --extensions-on-chrome-urls and --disable-extensions-except to "mitigate the risks associated with harmful and unwanted extensions".
- Automatic fallback to WebGL backed by SwiftShader is deprecated and WebGL context creation now fails instead of falling back to SwiftShader.
- Shared tab groups continues to roll out in Chrome 139. This enables the sharing of tab groups with other users.
You forgot to mention the fact that manifest v2 extensions can’t be manually enabled anymore using flags.
This commit is the most important, https://chromium.googlesource.com/chromium/src/+/6b2d509c86d688309dcf4a4c625b029849044322
Chrome 138 was the last version to support with policies v2 manifests for the full version of ublock origin.
>Remove manifest v2 availability policy
>This CL removes the ExtensionManifestV2Availability and
DeviceLoginScreenExtensionManifestV2Availability policies.
>These were temporary policies added for the MV2 deprecation. The
deprecation has since happened, the policies are no longer needed, and
we intend to remove them entirely from the code base.
Hopefully there will be forks that don’t follow suite.
fortunately –disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled flags still work to re-enable v2 extensions
Just please stop using Chromium based browsers.
@Scroogled,
Unfortunately, there is no better alternative. Everything else has inferior web standards support and questionable future.
Continue using Chromium based “Brave Browser”. It’s millions times better than Google Chrome