-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for browsers with Chromium 86 engine and lower #141
Comments
That error is almost certainly due to Chromium 86 not supporting Manifest V3, for chromium versions without Manifest V3 support you must use version 1.4.4.3 (or earlier) of chromium web store. |
this is pointless in any case, since even version 1.5.4 can no longer install anything from any of the add-on stores.(this is not true, more details in my post below) Chromium 102 also can't work with Manifest v3, just like Chromium 86, but they are both equally able to force add-ons installed with it, and they have the same chance of running something from it. the only difference is that 86th issues a warning that it is not fully ready to use Manifest v3. I don’t have any problems installing version 1.5.4.1 on Chromium 102, I just keep in mind that at least 50% of the add-ons with Manifest v3 most likely won’t work for me. |
and now, here are some interesting facts based on the test results. Chromium.Web.Store 1.4.4.3 allows you to install add-ons from the Edge Add-on Store, and even add-ons with Manifest v3, on Chromium 86. (their ability to work in this case is another matter, but the fact is that they can be installed) but from the New Chrome Store he cannot install anything even from add-ons with Manifest v2, because everything was changed there and now only newer browsers with Chromium.Web.Store 1.5.4 + can install something from there (I checked on 102 Chromium , all functionality of Chromium.Web.Store 1.5.4 works fine) conclusion: Google somehow intentionally limits the functionality of Chromium.Web.Store 1.5.4 +(and previous versions) on older browsers in the New Chrome store. at the same time, Chromium.Web.Store version 1.5.4 (on Chromium with engine 86 and lower) cannot do any of the above, even the one that I myself rebuilt for CentBrowser. it installs but does not function. Ideally, for older browsers we need an add-on with the capabilities of Chromium.Web.Store 1.4.4.3, but patched to the ability to install add-ons from the NEW Chrome store, bypassing Google's check for the browsers Chromium engine version, which is definitely there and functioning. (or simply make one version that will bypass Google checks for the version of the Chromium engine, and which will install any add-ons no matter what version of the manifest they work with. - on conditions(whatever can run, will run) [Thanks to Chromium.Web.Store 1.4.4.3, we now know that installing Manifest V3 add-ons is possible on browsers that are not technically suitable for this.] |
Thank you for all the info.
This is what I plan to do, but it may take me a minute. |
is there any news? |
I can't afford to spend a lot of time on this at the moment, but I made a quick attempt to bring the manifest v2 version up to feature parity. Things are almost certainly broken so please report any bugs you find so I can fix them. |
Ok, I tested this version. I am attaching it here too. Chromium.Web.Store v1.4.5 (src) CentBrowser ver (manifest v2 browsers).zip (archive with .crx file inside) |
my friend asked me “why he can’t install “chromium-web-store” v 1.5.4.1 on his browser with the Chromium 86 engine?”,
I checked it, and it’s true that the browser does not install version 1.5.4.1, it gives an error this type [Error Invalid value for 'web_accessible_resources[0]'. Failed to load manifest.]
You can still install version 1.5.4 on it, but as it turns out, at this moment it no longer installs the add-on from any of the stores (Chrome, Opera and Edge: the new Chrome Store has gray buttons, and in the Opera and Edge stores there is no reaction to pressing the buttons), so users of browsers below Chromium 86 are left deprived of the opportunity to install even though some extensions.
is it possible to do something about this?
The text was updated successfully, but these errors were encountered: