Google begins playing with extension Manifest V3 in Chrome 80 Canary build

Google begins playing with extension Manifest V3 in Chrome 80 Canary build

Despite the overwhelmingly negative reviews on the Manifest V3 extension program, Google stands firm on ad-blocking updates to Chrome. The company revealed last month that it has started testing its forthcoming extension manifest V3 in its new Chrome Canary build. The Manifest V3 developer preview is now available in the Chrome 80 Canary update as of October 31st.

Manifest v3 and why multiple ad blockers can cease

For many ad-block companies Manifest v3 has become a bone of contention. This is because Google developers have introduced an alternative to the webRequest API (formerly used for ad-blocking) named the declarative request API, which limits the webRequest API's block version. Chrome developers listed two reasons behind this new update, one of which was a performance (although this was nullified in a WhoTracks.me study) and the other was a better user privacy guarantee. Chrome already imposes a thirty thousand rule limit on it. But most common lists of ad-blocking rules use nearly 75,000 rules. Although Google said they were looking to increase that amount, they did not guarantee it.

Many ad blocker maintainers and developers felt the introduction of the declarativeNetRequest API could cause many already existing adblockers to be crippled.

Commenting on the original features of the webRequest API, the lead developer of the successful ad blocker uBlock Origin commented, "This breaks uBlock Origin and uMatrix, [which] are incompatible with the simple matching algorithm selected, ostensibly built to implement EasyList-like filter lists," he explained in an email to The Registry. "A blocking webRequest API allows open-ended content blocker designs, not limited to a specific design and limits dictated by the same company which claims content blockers are a threat to their business."

Many users have also mentioned that Chrome uses its browser market dominance to dictate what type of extensions are being developed and used? A user commented, "As Chrome is a dominant platform, it prevents our work from reaching users unless it aligns with Google's business goals, and extensions that users want on their devices are effectively censored out of existence."

Others said it's easier to skip all of the drama by simply switching to some other browser, Firefox in particular. “Or you could cease contributing to the Blink monopoly on the web and join us of Firefox. Within this vacuum, Microsoft is no longer challenging Google,' added a customer.

Changes suggested in Manifest V3

The Chrome team is continuing to iterate on the declarativeNetRequest API and its features as a part of Chrome 80 Canary development. Background service staff (killing background page and scripts) are now available to check in manifest version 2 and 3 extensions in Canary as part of this update. Restrictions on remote-hosted code and improvements to host permissions are currently a job underway. We also combine page action and browser action APIs with single-action API.

The proposed changes to manifest v3 are not yet finalized, and several features are currently underway. The stable release of MV3 is anticipated in 2020. As part of this launch, Google developed a V3 Migration to Manifest guide that can be used by developers to migrate their existing extensions. They also created a guide explicitly to move from the history pages to the service staff.

JOIN OUR WHATSAPP GROUP "TREASURE IS HERE" FOR LATEST JOBS & CORPORATE UPDATES @ https://chat.whatsapp.com/GrHGwkfC4eC98rnbTcCegM

Find top corporate Latest Job Updates: Click Here

Best Interview Tips: Click Here

Check out All Latest Jobs: Click Here

Top job Updates: Click Here 

How to Prepare  For Interview: Click Here

All technology Updates: Click Here

Best resume Building services:Click here