Google Chrome change that weakens ad blockers begins June 3rd
What specific changes does Google Chrome's Manifest V3 introduce to the extension platform compared to Manifest V2?
Google Chrome's Manifest V3 introduces several changes to the extension platform compared to Manifest V2. These changes aim to enhance the security, privacy, performance, and overall trustworthiness of Chrome extensions4. Here are the specific changes:
-
Limited extension access to user network requests: Manifest V3 introduces changes to the available APIs and adds new features. It removes the ability for an extension to use remotely hosted code, which presents security risks by allowing unreviewed code to be executed in extensions.
-
Forcing developers to include all functionality within the extension: This change ends the practice of hosting code remotely. With Manifest V3, an extension can only execute JavaScript that is included within its package and subject to review by the Chrome Web Store.
-
Moving network request modifications from the extensions to the browser: Manifest V3 moves the background context to service workers, which run only when needed. This change improves browser performance.
-
Replacing background pages with dedicated service workers: This change also contributes to improving browser performance.
While these changes appear positive for end-users, they introduce major technical challenges for extension developers, especially for those who need greater control over browser functions, such as ad-blockers. These developers now have to implement complex mechanisms to remain effective.
Why will rulesets no longer be frequently updated in the new Manifest V3 extensions?
In the new Manifest V3 extensions, rulesets will no longer be frequently updated due to changes in the extension platform3. Unlike Manifest V2, where rulesets could be updated automatically by the extension, Manifest V3 requires rulesets to be updated only when new versions of the extension are released3. This change is part of Google's effort to enhance the security, privacy, performance, and trustworthiness of Chrome extensions by limiting extension access to user network requests and forcing developers to include all functionality within the extension. However, this also means that for more advanced uses, users may need to configure additional settings or give extra permissions to specific sites.
What measures has Google implemented to assist developers in transitioning from Manifest V2 to Manifest V3?
Google has implemented several measures to assist developers in transitioning from Manifest V2 to Manifest V3. These measures include:
-
Providing a migration guide: Google has published a migration guide covering everything developers need to know to successfully migrate their extensions from Manifest V2 to Manifest V3.
-
Introducing new features and functionality: Google has added new features to the platform, such as the Side Panel API and the Reading List API, to improve the overall extension development experience.
-
Addressing developer feedback: Google has made changes to Manifest V3 based on developer feedback, including introducing Offscreen Documents, providing better control over service worker lifetimes, and adding a new User Scripts API.
-
Collaborating with the extension developer community: Google has worked closely with extension developers, taking their feedback into account and making iterative improvements to Manifest V3.
-
Offering support channels: Google has provided support channels for developers who have questions or encounter issues during the migration process. Developers can post their queries or concerns to the chromium-extensions Google Group.
-
Allowing review skipping for safe rule updates: Google now allows extensions to skip the review process for "safe" rule set changes, making it easier for developers to update their extensions without delays.
-
Expanding the number of allowed rulesets: Google has expanded the number of allowed rulesets for the declarativeNetRequest API, which helps ad-blockers and other content-filtering extensions.
Through these measures, Google aims to facilitate a smooth transition for developers from Manifest V2 to Manifest V3 and ensure the continued security, privacy, performance, and trustworthiness of Chrome extensions.