SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Alphabet Inc. (Google)
GOOGL 1,466-1.2%Jan 24 4:00 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
From: TimF11/13/2019 10:38:34 PM
   of 15330
 
Google has begun testing their upcoming extension manifest V3 in the the latest Chrome Canary build, and with this initial 'alpha' release, developers can begin testing their extensions under the upcoming specification.

In a post to the Chromium Extensions Google group, Simeon Vincent, a Google Developer Advocate for Chrome Extensions, stated that as of October 31st a developer preview of the extension manifest v3 is now available in the Chrome 80 Canary build.

"Think of it as an early alpha. The "dev preview" is the first opportunity for extensions developers to start experimenting with a work-in-progress version of the MV3 platform.

We're far from finished with the implementation work on the MV3 platform, so first and foremost expect changes.

As for what's changing, the four big-ticket items in MV3 are:
  • Host permissions changes
  • Blocking webRequest -> declarativeNetRequest
  • Background page -> service workers
  • Remotely hosted code restrictions"
The declarativeNetRequest API has already been available for experimentation in Chrome Canary and we're continuing to iterate on it's capabilities

As part of this launch, Google has created a Migrating to Manifest V3 guide that developers can use to migrate their existing extensions.

The most controversial aspect of the extension manifest v3 is the upcoming changes to the webRequest API. In v3, Google has changed the API so that extensions can only monitor browser connections, but not modify any of the content before it's displayed.

Instead Google wants developers to use the declarativeNetRequest API, which has the browser, not the extension, strip content or resources from a visited web sites. This API, though, has a limit of 30,000 rules that can be created.

Unfortunately, this change will break popular ad blockers such as uBlock Origin, which rely on the original functionality of the webRequest API and need more rules than are available in the declarativeNetRequest API.

bleepingcomputer.com
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext