+- CentBrowser Forum (https://www.centbrowser.net/en)
+-- Forum: Product Related (https://www.centbrowser.net/en/forumdisplay.php?fid=1)
+--- Forum: Bugs & Suggestions (https://www.centbrowser.net/en/forumdisplay.php?fid=4)
+--- Thread: do not update to Chrome Extension Manifest V3 (/showthread.php?tid=2619)
Pages:
1
2
RE: do not update to Chrome Extension Manifest V3 - Zidichy - 05-31-2019
I am also very interested to know how this will affect centbrowser.
btw im happy i left chrome when i did and switch to centbrowser, i had a feeling google would do something like this.
installed cent on 12/05/19
Don't know if you guys saw this but,
https://9to5google.com/2019/05/29/chrome-ad-blocking-enterprise-manifest-v3/
RE: do not update to Chrome Extension Manifest V3 - patrickdrd - 06-07-2019
there's a workaround already for manifest v3:
Quote:What happened?
Chrome decided to deprecate the blocking capabilities of the webRequest API in Manifest V3, not the entire webRequest AP! This manifest does not only break ad-blockers, it also affects other extensions such as Tampermonkey.
The official Manifest can be found here.
Which Chrome(ium) based Browser are not affected?
Brave promised to revert the new webRequest API changes. See also here. Vivaldi also promised to take action.
Using ad-block(er) does not require an "Enterprise Chrome version"
There are several wrong news spread around the internet that ad-blocking needs a "special Enterprise" version, this is totally wrong.
About the Enterprise version
The "Enterprise" version is basically spoken just a normal Chrome version packaged as an .MSI for easy deployment using some kind of software distribution tool. The tool itself is closed source.
What people need is a Windows version which (officially) deploy some type of Group Policy to enable this. Typically that's a Windows 10 Pro/Enterprise version which comes with (gpedit.msc) the Group Policy Editor.
Windows 10 Home users can install gpedit manually. There are also unofficial tools to enable it.
"Unlocking" Ad-Blocking after Manifest V3
Download the Chrome "Enterprise version" (the .msi) file.
Download the Policy and preferences templates (it's not yet updated).
Import the .admx template. I assume MacOS/Linux users getting a separate template (speculation). I will upload them here.
That's pretty much it.
https://github.com/CHEF-KOCH/Chromium-hardening/blob/37204ecf2c54aaff26dd99cd7700ddf37a3b7ff4/Docs/Using%20ad-blockers%20after%20Manifest%20v3.md
RE: do not update to Chrome Extension Manifest V3 - Admini - 06-08-2019
(06-07-2019, 09:15 AM)patrickdrd Wrote: there's a workaround already for manifest v3:
Great news, thanks.
If this solution works, this change should not be hard coded and there may be switches can be used in the code base.