SoylentNews is people
SoylentNews
Mozilla reaffirms that Firefox will continue to support current content blockers - gHacks Tech News:
From next year onward, extensions for Google Chrome and most other Chromium-based browsers, will have to rely on a new extension manifest. Manifest V3 defines the boundaries in which extensions may operate.
Current Chromium extensions use Manifest V2 for the most part, even though the January 2023 deadline is looming over the heads of every extension developer.
[...] By June 2023, Chrome and most Chromium-based browsers won't support Manifest v2 extensions anymore. Those installed will be disabled automatically, because they are no longer compatible. Those offered on the Chrome Web Store will vanish, unless their developers published an update to make them compatible with the new Manifest v3.
[...] While Manifest v3 does not mean the end for content blocking on Chrome, Edge and other Chromium-based browsers, it may limit abilities under certain circumstances. Users who install a single content blocker and no other extension that relies on the same relevant API may not notice much of a change, but those who like to add custom filter lists or use multiple extensions that rely on the API, may run into artificial limits set by Google.
[...] Mozilla reaffirmed this week that its plan has not changed. In "These weeks in Firefox: issue 124", the organization confirms that it will support the WebRequst API of Manifest v2 alongside Manifest v3.
[...] That is good news for users of the web browser who use content blockers such as uBlock Origin. The extension, which its developer claims operates best under Firefox, is the most popular extension for Firefox based on the number of installations and ratings.
(Score: 3, Interesting) by bobthecimmerian on Friday September 30 2022, @12:42AM
Mozilla had to abandon their previous extension API to go multi-process, and they had to go multi-process because they were losing browser performance wars to Google badly.
They're still losing, partly because Google throws more money at the problem than Mozilla can afford to match and partly because Baker appears to be an idiot and not make performance a bigger priority. But the performance gap is a fraction of what it was when Firefox had its old extension APIs.