You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prodlem
When using fc-chromium-policies, we restrict ourselves to those settings that are registered in it. Also, for the chromium logger to work correctly, you need to track changes to its settings with each chromium update in order to update them in logger policy. This is not very convenient.
Decision
I suggest making the following changes, at startup the fc-logger will take a snapshot of the file with chromium settings and take it as its initial state. Then it will compare the changed parameters with the original state and save the changes. I also propose making a policy with filters of settings, that is, a policy similar to an existing one, which filter out chromium extra settings can be added.
The text was updated successfully, but these errors were encountered:
Prodlem
When using fc-chromium-policies, we restrict ourselves to those settings that are registered in it. Also, for the chromium logger to work correctly, you need to track changes to its settings with each chromium update in order to update them in logger policy. This is not very convenient.
Decision
I suggest making the following changes, at startup the fc-logger will take a snapshot of the file with chromium settings and take it as its initial state. Then it will compare the changed parameters with the original state and save the changes. I also propose making a policy with filters of settings, that is, a policy similar to an existing one, which filter out chromium extra settings can be added.
The text was updated successfully, but these errors were encountered: