Another month, another Chrome update — and this time, we’ve landed on Google Chrome version 139 (build 139.0.7258.66/67). While this update might seem quiet on the surface, it brings some subtle yet important changes behind the scenes — especially for developers, Android users, and those still clinging to Manifest V2 Chrome extensions like uBlock Origin.
In this detailed article, we’ll break down everything you need to know about Chrome version 139 — including:
- Security updates and patch details
- Major OS support changes on Android
- Developer and performance improvements
- The future of Manifest V2 extensions
- The anticipated (but still absent) split-screen feature
Let’s dive in — and by the end of this article, you’ll know exactly how this Chrome release affects you.
First Things First: How to Check If You’re Running Chrome 139
Before we start discussing what’s changed, let’s make sure you’re actually running Chrome version 139.
To check your version:
- Open Chrome.
- Click the three-dot menu in the upper-right corner.
- Go to Help > About Google Chrome.
- Chrome will auto-update if a newer version is available.
- You should now see:
Version: 139.0.7258.66 (or .67 depending on your OS)
This version is now rolling out across Windows, macOS, and Linux.
So Far So Good… Let’s Talk About the Security Fixes
Google Chrome version 139 includes 12 security fixes, a pretty standard count for a typical monthly release. The good news? There are:
- No critical vulnerabilities
- No zero-day exploits reported
- No high-severity bugs
Only a mix of medium and low-severity issues were patched. For everyday users, this means a stable and secure browser experience without any emergency security drama.
Why does this matter?
Security patches are one of the main reasons you should always keep Chrome updated. Even if there aren’t flashy new features, behind-the-scenes fixes can prevent dangerous exploits before they affect you.
Let’s Move to the Next Step: Android Version Support Change
A significant shift has happened on the mobile side of things.
Here’s the change:
- Chrome 138 was the last version to support:
- Android 8 (Oreo)
- Android 9 (Pie)
- Chrome 139 and beyond now require Android 10 or higher.
If you’re using an older Android device that hasn’t received an update to Android 10, you won’t be able to install or update to Chrome 139+.
What can you do?
- Check your Android version via Settings > About Phone > Android Version
- If stuck on Android 8/9, consider using an alternative browser like Firefox or Brave, which may continue supporting older Android versions longer.
Developers, Pay Attention: Bug Fixes and Web Behavior Updates
While there’s not much in terms of visual or front-end features for end users, Chrome 139 includes several bug fixes and optimizations aimed at web developers.
Improvements include:
- Performance enhancements for web rendering
- Minor bug fixes in developer tools
- New experimental CSS capabilities, like:
- More advanced corner shapes
- Smoother animation support
These features might not affect what you see on a daily basis just yet — but they empower developers to create faster, cleaner, and more interactive web apps and websites.
So if you’re a developer, this version lays groundwork for better things to come. And if you’re a user, your favorite sites may just get faster or more polished soon.
Still Missing: Where is the Split View Feature?
Chrome Canary has had a split-screen preview feature for some time — allowing two tabs side by side in a single window — but unfortunately, it hasn’t made its way into the stable version with Chrome 139.
Many users hoped split view would roll out with this release, but it’s still not here. That said, it’s likely coming soon — perhaps in version 140 or 141 — so keep an eye out.
Now the Big One: Manifest V2 Is Officially Deprecated
If you’re using Chrome extensions like uBlock Origin, pay close attention.
Here’s what’s changed:
- Chrome 139 officially deprecates Manifest V2 extensions.
- All extensions are now required to use Manifest V3.
- Flags (temporary experimental switches) that previously enabled V2 workarounds have now been removed.
What is Manifest V2 and V3?
- Manifest V2: Allowed extensions more powerful access to filter content and interact deeply with the browser (used by uBlock Origin and similar tools).
- Manifest V3: Introduces more restrictions for performance and privacy — but also breaks several advanced ad-blocking features.
Impact:
- uBlock Origin (V2) still works in Chrome 139 using a few hidden tweaks.
- Those tweaks likely won’t work in Chrome 140, which removes these flags entirely.
- Manifest V3-compatible versions of extensions may not offer the same power or features.
Resolve… AdBlockers Killed by Chrome: How to Fight Back and Reclaim Your Browser Privacy in 2025
What can users do?
- Consider switching to browsers like Firefox, which still support full-featured ad-blockers.
- Or try alternative Chromium-based browsers like Brave, which offer built-in blocking capabilities.
Frequently Asked Questions (FAQ)
Q1: How can I keep using uBlock Origin in Chrome?
Currently, with version 139, it’s still possible using a few experimental flags and configuration tweaks. However, this is likely your last chance to use those workarounds before they are removed in Chrome 140.
Q2: Will Chrome force-disable Manifest V2 extensions?
Yes. Eventually, Chrome will no longer allow V2 extensions to run at all — even with workarounds. This enforcement is already active in Canary and Dev builds.
Q3: What is Manifest V3 good for?
Google argues that V3 improves browser performance and security by restricting overly powerful APIs. However, privacy advocates and developers argue that it limits user control, especially for content filtering tools.
Q4: What about other browsers like Edge, Opera, Brave?
Since they’re based on Chromium, these browsers will also eventually adopt Manifest V3. However, some (like Brave) have added extra layers to preserve advanced ad-blocking.
Final Thoughts: A Subtle but Important Update
While Chrome version 139 might feel like a quiet release, it’s actually laying foundations for major shifts:
- Android users with older phones may lose access to Chrome updates
- Developers benefit from more power and performance under the hood
- Manifest V2 extensions are nearing extinction
- Split-screen remains a “coming soon” feature
So even though there’s no flashy UI overhaul or visible new feature in this update, Chrome 139 marks a turning point — especially for privacy-minded users and developers.
Whether you’re a casual Chrome user or a developer building the next big web app, it’s a good idea to stay informed about these behind-the-scenes changes.
Tags: chrome version 139, google chrome update, manifest v2 deprecated, ublock origin chrome, chrome security fixes, android 10 chrome support, chrome css updates, developer features chrome, chromium extension changes, chrome 139 review
Hashtags:
#Chrome139 #GoogleChromeUpdate #ManifestV3 #UblockOrigin #BrowserExtensions #WebSecurity #Android10 #ChromiumBrowser #WebDevNews #PrivacyTools
Disclaimer:
This article is for informational purposes only and does not endorse or guide users toward enabling unsupported or deprecated features. Chrome flags and experimental settings may change or be removed at any time. Use them at your own risk. Always install browser updates from the official Google Chrome website.
