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

[SanitizeOnShutdown (Selective) > Locked] *privacy.history.custom* not set #1035

Open
htcfreek opened this issue Jul 20, 2023 · 2 comments
Open

Comments

@htcfreek
Copy link
Contributor

htcfreek commented Jul 20, 2023

Setting the Locked value for "SanitizeOnShutdown (Selective)" to Enabled should lock the drop-down in the settings ui and the corresponding preference too. If the selective sanitize is enabled the user can't change the drop-down, so it should be disabled to prevent confusion.

The missing/required preference setting ist:

"privacy.history.custom": {
"Value": true,
"Status": "locked"
}

image

By the way, this preference is blocked in the preferences GPO for stability reasons. For me this makes no sense as there are no stability reasons and there is a menu in the settings ui.

@mkaply
Copy link
Collaborator

mkaply commented Jul 20, 2023

The "stability reeasons" is a generic message that we use for preferences that aren't supported.

Which dropdown are you referring to? The custom settings for history dropdown controls other things.

@htcfreek
Copy link
Contributor Author

htcfreek commented Jul 20, 2023

Which dropdown are you referring to? The custom settings for history dropdown controls other things.

Exactly this one. The user can select "Never clear" and "Clear all (like private mode)". But the drop-down always switches back to "Custom mode" if a selective sanitize setting is set via policy.

And btw. the settings ui feels a bit confusing here. (See #1038.)

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

2 participants