Update com.google.Chrome.plist

[BigMacAdmin]

Adding 4 new "privacy sandbox ad controls" for Google Chrome

https://chromeenterprise.google/policies/#PrivacySandbox

[relgit]

Thank for the submission; the changes look good to me. Now we just need to have pfm_version bumped, pfm_last_modified updated, the new keys added to pfm_segments, and we're good to go.

[BigMacAdmin]

@relgit
Is the pfm_segments array the deciding factor that determines which tab a configuration key is displayed under?
If so, and additionally: I've added 4 new keys for the Google Chrome profile related to ad privacy. Which tab would these be appropriate for? Misc. or maybe Content Settings? Or does this justify an entirely new tab for "Privacy" or "Ad Tracking"?

[relgit]

Yes, pfm_segments determines that tab that subkeys appear under.

I can see that Google chose to group these new four subkey on their own and not as part of the Misc. group, and honestly Misc. is already very crowded, so yes, lets create a new Privacy Sandbox group. To create a new group you'll need to also amend the PFC_SegmentedControl_0 subkey.

[BigMacAdmin]

There must be something I'm missing, I've followed your instructions but I cannot seem to get a new "Privacy Sandbox" group created.

The new keys still show in the "Other" section within iMazing Profile Editor.

[relgit]

That's OK. I'm assuming this was tested on iMazing Profile Editor, which has a grouping override on the Chrome manifest. To show the actual grouping that's in the manifest, you can untick Process custom manifests for optimal display in iMazing Profile Editor (recommended) in the app settings.
The override will be updated in the next release to fall in line with this pull request.

Now, the grouping changes look good, but have a look please at my comments for two small issues that require addressing.

Thanks!