Firefox matches the changes to the Chrome browser extension in the security name

Two years later Google proposed and adopted changes to its Web browser extension frame, Firefox is ready to follow suit, but with one exception.
Known collectively as Manifest v3, the changes addressed many security issues with the browser’s existing framework, which allowed extensions to override the browser security model and recover sensitive data.
While Manifest v3 created incompatibilities between Chrome and Firefox, the latter decided to wait and follow the evolution of the framework before adopting it.
We take a look at how our readers are using VPN for an upcoming in-depth report. We would love to hear from you in the poll below. It won’t take more than 60 seconds of your time.
âAs we wrote previously, we want to maintain a high degree of compatibility to support cross-browser development. We will be introducing Manifest v3 support for Firefox extensions, âFirefox developers shared in a blog post.
WebRequestAPI
Firefox developers were quick to add that while they will adopt Manifest v3, their implementation will differ from Chrome in some areas where Firefox believes its “values ââindicate a different solution.”
When it released Manifest v3 in 2019, Google claimed this was one of the biggest changes in the extensions platform and offered extensions using security, privacy and performance. improved.
However, Manifest v3 deprecated some features of WebRequestAPI that ad blocking extensions such as uBlock Origin and Ghostery rely on to work.
In their Manifest v3 implementation plans, the developers of the popular Open source Web browser shared that after discussions with several developers of content blocking extensions, they have decided to retain support for WebRequestAPI blocking capabilities with Google’s replacement, called decalarativeNetRequest (DNR).
“We will support blocking webRequest until there is a better solution that covers all of the use cases that we consider important, since DNR as currently implemented by Chrome is not responding yet. to the needs of extension developers, âFirefox wrote.
Going through The register