Skip to content
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

Please read this... Explanation on using policies for extensions according Chromium.org recomnadations #1068

Open
bontinckd opened this issue Dec 5, 2019 · 0 comments

Comments

@bontinckd
Copy link

Hoi,

Possibly it is related to other issues, but to help, I would like to provide following info...

Managing Chrome settings on windows can be via 3 ways:

  1. directly via the registry
  2. using local policies via the local policy editor
  3. Using GPO's on a windows Active directory

(end the end GPO's and local policies result in Registry settings applied on a windows system)

Option 1 can be used also via GPO's by importing a registry-file with the correct settings

For option 2 & 3 you need the google chrome admx-files being placed in the windows C:\Windows\PolicyDefinitions location to be able to use them in the windows Group Policy Management Editor via "Computer Configuration/Policies/Administrative Templates"

Consulting the Chromium.org website I found following info:
https://www.chromium.org/administrators/configuring-policy-for-extensions.
This rule tells where to store in the Registry Policies for extensions, meaning specific settings for a certain extension. You will see that the ID of the extension is used.

Now I can understand that you have made a solution that easily runs on multiple platforms by not using the Windows registry. But Chromium based browsers like Google Chrome and Mozilla Firefox are heavily using the Windows-registry, and can be deployed via GPO's, so it is really a pitty that your extension is not using it also.

Like thousand other system engineers I hope you give priority to implement the Chromium.org recommandations. Because your TGS works better then the native tab discard method from Chrome. TGS, releases more memory !!!

DannY.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant