Chrome Manifest V3 Release Date: What You Need to Know

Author

Reads 1.3K

A focused engineer organizing tools in a vibrant workshop setting.
Credit: pexels.com, A focused engineer organizing tools in a vibrant workshop setting.

Chrome Manifest V3 is a significant update to the Chrome extension ecosystem, and it's essential to know what's changing. The new version is expected to be released in early 2023.

Manifest V3 brings a new set of APIs that will replace the current webRequest API. This change is aimed at improving security and performance.

The new APIs will provide more granular control over permissions and will help prevent malicious extensions from accessing sensitive user data.

If this caught your attention, see: New Apple Phone Release Date

Chrome Manifest V3 Release Date

Google announced major changes to the Chrome extensions ecosystem back in October 2018, which led to the creation of Manifest V3.

The changes were detailed in a document published last year, but it wasn't until January of this year that the maintainers of several ad blocker extensions raised issues with the new API function.

Starting July/August, users will be able to test how their favorite extensions behave in Chrome Canary.

Opera, Brave, and Vivaldi have said they plan to ignore Chrome's anti-ad-blocker changes, despite the shared Chromium codebase.

Google has always said the primary reason for Manifest V3 has been protecting user privacy and security, not crippling ad blockers.

Google Chrome Extension Platform Updates

Credit: youtube.com, Google’s New Chrome Update is Breaking Extensions! 😡 Manifest V3 is a Major Change!

Google Chrome is shutting down its current extension platform, Manifest v2, and replacing it with Manifest v3. This change will impact content filtering, which is an essential process for ad blockers and anti-tracking extensions.

Extensions running Manifest v2 will lose their "featured" status in the Chrome Web Store and will no longer be able to download any new extensions from the Chrome Web Store. Any relevant extensions that you have installed will be automatically disabled.

The transition has resumed in June 2024 in beta versions of Chrome, and it will not impact the majority of users for at least another month. This is because the level of testing required in the beta versions of Chrome during the transition phase means that it will not impact the majority of users for at least another month.

Curious to learn more? Check out: He Texted after First Date but Not since

Impact on Extensions

The impact on extensions is significant. Many popular ad blockers, such as uBlock Origin, will no longer be available for download from the Chrome Web Store once the transition is complete.

Close-Up Shot of App Icons
Credit: pexels.com, Close-Up Shot of App Icons

Extensions running Manifest v2 will automatically be disabled, and users will need to seek alternatives before they are permanently disabled. This includes many actively maintained extensions in the Chrome Web Store.

The new Manifest v3 system will limit content filtering, which is essential for ad blockers and anti-tracking extensions. This has sparked controversy and scepticism within the tech community.

Users may need to switch to Firefox or another browser to run the most effective ad blockers and tracking limiters, as Mozilla has stated it will support Manifest v3 with some key differences in implementation.

Explore further: Google Ad Blocker Iphone

New Features

The Google Chrome Extension Platform has just gotten a whole lot better with the latest updates.

One of the most exciting new features is the ability to use the WebExtensions API to create extensions that can interact with web pages in new and powerful ways. This means developers can now create more complex and functional extensions that really make a difference.

Credit: youtube.com, 4. How to Update a Google Chrome Extension | Step-by-Step Guide

Extensions can now use the "declarativeContent" API to specify how they want to handle certain types of content, making it easier to manage complex scenarios. This is a huge improvement over the old way of doing things.

Another big update is the addition of the "chrome.identity" API, which allows extensions to use the user's Google account to authenticate and authorize access to sensitive data. This is a game-changer for developers who need to handle authentication in their extensions.

The new "chrome.tabs" API also deserves a mention, as it makes it much easier for extensions to manage tabs and interact with web pages in a more seamless way. This is especially useful for extensions that need to perform complex tasks, like data scraping or automation.

Overall, these new features are going to make it much easier for developers to create powerful and functional extensions that really make a difference for users.

Known Issues

The Google Chrome Extension Platform has its share of known issues. One of the most common problems is the lack of support for legacy APIs, which can cause compatibility issues with older extensions.

Credit: youtube.com, About Google Chrome's "This extension may soon no longer be supported"

Extensions that rely on deprecated APIs may not work properly, leading to frustrating user experiences.

The Chrome team is actively working to phase out these legacy APIs, but it's essential for developers to update their extensions to use the latest APIs.

The limited storage space available to extensions can also cause issues, especially for those that need to store large amounts of data.

This can lead to extensions that are unable to function properly, resulting in a poor user experience.

To mitigate this issue, developers can consider using alternative storage solutions, such as the Chrome storage API.

Another known issue is the lack of support for certain types of content, including certain types of videos and audio files.

Extensions that rely on these types of content may not work as expected, leading to user frustration.

The Chrome team is working to address these issues, but in the meantime, developers can consider using alternative content types or finding workarounds.

Extensions that use the "activeTab" permission may experience issues with the new tab navigation model.

This can cause extensions to malfunction or not function at all.

Developers can update their extensions to use the "activeTab" permission with the "replace" option to resolve this issue.

The Chrome team is actively working to resolve these known issues and improve the overall extension platform.

A unique perspective: Google Chrome Local Storage Limit

Frequently Asked Questions

Why is Google pushing Manifest V3?

Google is pushing Manifest V3 to improve browser extension security, privacy, and performance by enforcing stricter technical limitations. This change may also limit the effectiveness of ad-blockers, aligning with Google's interests.

Will arc be affected by manifest V3?

Unfortunately, Arc will be impacted by Manifest V3, which may cause some ad blocking extensions, like uBlock Origin, to stop working

Gilbert Deckow

Senior Writer

Gilbert Deckow is a seasoned writer with a knack for breaking down complex technical topics into engaging and accessible content. With a focus on the ever-evolving world of cloud computing, Gilbert has established himself as a go-to expert on Azure Storage Options and related topics. Gilbert's writing style is characterized by clarity, precision, and a dash of humor, making even the most intricate concepts feel approachable and enjoyable to read.

Love What You Read? Stay Updated!

Join our community for insights, tips, and more.