Chrome Web Store migration plan? #2977
-
Has @gorhill or anyone else stated the exact plan for the current Chrome Web Store listing of uBlock Origin? Will it be updated to the Manifest V3-compliant Lite version, or will people have to install the Lite version on their own? |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 41 replies
-
I haven't decided yet how this will work, and I don't know what is feasible. Forcing uBO Lite on people might not be the best move, as this would essentially obliterate all customization they might have made to uBO -- uBO Lite is too different from uBO to make a seamless transition. People can already move on their own to uBO Lite if they want, probably safest approach is to explicitly opt-in to uBO Lite, some might prefer to install a another MV3-based content blocker. |
Beta Was this translation helpful? Give feedback.
-
I am re-opening this because I still have final decisions to make. Here is the official Manifest V2 (MV2) deprecation timeline: https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline
This means that starting July 2024, uBO could be disabled/removed at any time. However, there is a way in Chromium-based browser to extend availability of MV2 to June 2025:
I did experiment with file: content: {
"ExtensionManifestV2Availability": 2
} For other OS, the way to set policies will be different. Result: So if this is a valid way to extend uBO's life time in Chromium-based browsers, users will have to set this policy in their browser. Possible the community could come up with tools so that users with little to no technical knowledge can use these. More details on how to set that policy in all OSes: https://chromeenterprise.google/policies/#ExtensionManifestV2Availability. Note that setting that policy raise a warnign in the browser: There are still questions to be answered:
|
Beta Was this translation helpful? Give feedback.
-
Here is how to enable
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ExtensionManifestV2Availability</key>
<integer>2</integer>
</dict>
</plist>
python3 ./mcxToProfile.py --plist com.google.Chrome.plist --identifier [UUIDv4] Replace the UUID with your own randomly generated UUID! And remember that UUID, you should always use the same UUID when creating the updated policy later.
![]() For the obvious reason, I won't upload my already generated |
Beta Was this translation helpful? Give feedback.
-
At Brave we're planning to keep alive the option to keep allow users to install select MV2 extensions
@gorhill Would it be possible to keep updating the MV2 Chrome crx extension post transition. If not in the play store. via Github? |
Beta Was this translation helpful? Give feedback.
-
Simply writing the policy preference item to the plist of Chrome or Brave seems to work fine in MacOS: Chrome Chrome Beta Brave Brave Beta |
Beta Was this translation helpful? Give feedback.
-
For Vivaldi: run this vivaldi-stable --enable-features=ExtensionsManifestV2 for Linux works |
Beta Was this translation helpful? Give feedback.
-
Thanks to Chrome Web Store removing the featured badge from manifest v2 extensions, people are now being sent to the scammy "ublock" This may be solved by nominating uBlock Origin Lite for the featured label |
Beta Was this translation helpful? Give feedback.
I haven't decided yet how this will work, and I don't know what is feasible. Forcing uBO Lite on people might not be the best move, as this would essentially obliterate all customization they might have made to uBO -- uBO Lite is too different from uBO to make a seamless transition. People can already move on their own to uBO Lite if they want, probably safest approach is to explicitly opt-in to uBO Lite, some might prefer to install a another MV3-based content blocker.