Xopus

Main Menu

  • Schemas
  • CSS
  • Chrome
  • Firefox
  • Fund

Xopus

Header Banner

Xopus

  • Schemas
  • CSS
  • Chrome
  • Firefox
  • Fund
Firefox
Home›Firefox›Firefox matches the changes to the Chrome browser extension in the security name

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

By Warren B. Obrien
May 28, 2021
0
0



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.

TechRadar needs you!

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.

>> Click here to start the survey in a new window

“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



Related posts:

  1. Find out if your browser supports the new JPEG XL image format
  2. Microsoft Edge blocks Firefox installer, says it will harm your PC
  3. Mozilla makes big changes to Firefox updates
  4. Firefox is the best browser for PC gamers
Tagsweb browser

Recent Posts

  • This Keyboard Shortcut Can Undo Your Most Annoying Browser Mistake
  • UCSF and I-SPY 2 breast cancer researchers develop newly redefined breast cancer response subtypes
  • India-based web design company promises free food to children in need
  • Global Chromium Powder Market Size 2022 Booming By Share, Growth Size, Scope, Key Segments And Forecast To 2029 – Industrial Computing
  • Google Search Adds Author Markup Best Practices

Archives

  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021

Categories

  • Chrome
  • CSS
  • Firefox
  • Fund
  • Schemas
  • Terms and Conditions
  • Privacy Policy