Separate policy key #734
Labels
enhancement
New feature or request
Comments
|
The browser already have its own policy key as "Supermium", which I use to set various settings, which works fine. |
|
no one need not portable browser |
|
All internal branding was changed to Supermium (or Supemium for "Default Programs" for compatibility for Windows 8 and above) a long time ago, which should've included all registry keys. Either Chromium or Supermium reg keys should be usable, not both. I'll look into this problem. |
|
I guess, the browser may use both Chromium-related and own registry key for policy, which isn't good - each software should be manageable with the dedicated policy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In short: the browser should have a separate registry key for its policy-related settings.
Version 124.0.6367.245 uses policy for Chromium (which is under
HKEY_LOCAL_MACHINE\Software\Policies\Chromium).For instance, if
ExtensionInstallForcelistlists some extensions there, they will be automatically installed for Supermium as well.In general the policy may work fine (so Supermium can be used as a drop-in replacement for Chromium), but in certain cases it may lead to undesired side-effects.
Case 1 - Installing unsupported extensions
ExtensionInstallForcelistin my case (Windows 8.1 64-bit) lists Volume Master - outdated browsers edition (it is to be used on Chromium 115 and older), because I still run Chromium 109.0.5414.120 (it is the last version, which supports Windows 8.1).So far this old version of extension works fine with Supermium 124.0.6367.245, but since the browser is evolving older extensions may stop working some day.
The text was updated successfully, but these errors were encountered: