In Manifest V3, the use of this API will be limited in its blocking form. The basic flow of handling a request using this API is, Chrome receives the request, asks the extension, and then gets the result. The webRequest API permits extensions to intercept requests to modify, redirect, or block them. Users speculated that probably this outcome is the result of the “crippling” update Google has introduced in Chrome (beta and dev versions currently): deprecating the blocking ability of the WebRequest API. This news sparked a discussion on Hacker News and Reddit. Actually, logic dictates that 1.22.5rc0 should also be rejected and yet it’s still available in the Chrome Web Store.” Users’ reaction on Google rejecting the uBlock Origin dev build He commented, “I will upload stable to the Chrome Web Store, but given 1.22.5rc2 is rejected, logic dictates that 1.23.0 will be rejected. He does plans to upload the stable version. Hill on a GitHub issue mentioned that this is basically “stonewalling” and in the future, users may have to switch to another browser to use uBlock Origin. An email to Hill from Google reads, “Do not create an extension that requires users to accept bundles of unrelated functionality, such as an email notifier and a news headline aggregator.” Google stated that the extension did not comply with its extension standards as it bundles up different purposes into a single extension. uBlock Origin is a free and open-source browser extension widely used for content-filtering and adblocking. Last week, Raymond Hill, the developer behind uBlock Origin shared that the extension’s dev build 1.22.5rc1 was rejected by Google’s Chrome Web Store ( CWS ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |