Proxy chrome extensions are not going to be usable in MV3

1. ladybird

   1 20 1,562 8.9 C++

   Discontinued The Ladybird web browser (by SerenityOS)

   

   Something like Ladybird? https://github.com/SerenityOS/ladybird

   I think it wants to implement all of JS eventually though.

2. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

3. Surfingkeys

   2 41 5,637 7.6 JavaScript

   Map your keys for web surfing, expand your browser with javascript and keyboard.

   

   Manifest V2 deprecation is likely going to break extensions that inject userscripts, like Tampermonkey [0] and SurfingKeys [1]. The Chrome team has been rather unhelpful. They've promised to add support for power-user tools like these in MV3:

   dotproto from the Chrome team commented on May 27 [2]:

   > @mon-jai, the short answer is no, I don't have any updates to share. That said, I'll reaffirm that we plan to support userscript managers in Maniest V3 before the Manifest V2 deprecation.

   But the deprecation is approaching and the Chrome team hasn't released any more information about this AFAIK. These extensions are going to require large refactors to support MV3 and they can't meaningfully start until the Chrome team elucidates how script injection will work. With MV2 deprecation coming so soon, I worry there won't be enough time.

   [0]: Manifest V3: examine the effects · Issue #644 · Tampermonkey/tampermonkey: https://github.com/Tampermonkey/tampermonkey/issues/644

   [1]: Migrate to Manifest V3 · Issue #1821 · brookhong/Surfingkeys - https://github.com/brookhong/Surfingkeys/issues/1821

   [2]: https://github.com/Tampermonkey/tampermonkey/issues/644#issu...

4. browser_extension

   3 175 3,462 9.2 JavaScript

   A browser extension that redirects popular sites to alternative privacy friendly frontends

   

   I keep seeing sentences like "MV3 is approaching", "when MV3 drops in x months", but the reality is that MV3 is already here and affecting extensions!

   New extensions that use MV2 have been unabled to be added to the store [1] and this has already affected some extensions which, as a result, have to be installed manually [2]

   The time to switch to Firefox is right now.

   [1] https://developer.chrome.com/docs/extensions/mv2/

   [2] https://github.com/libredirect/libredirect/issues/45#issueco...

5. webextensions

   4 38 642 8.5 Bikeshed

   Charter and administrivia for the WebExtensions Community Group (WECG)

   

Suggest a related project