To the casual reader, two methods on ContentBrowserClient would imply that the corresponding features are gated on cookie settings. In fact, however, the corresponding features no longer exist.

-- ContentBrowserClient::AllowSaveLocalState

This was used for NPAPI plugins (primarily: Flash) to turn on in-memory storage for Local Shared Objects if cookie content settings were set to session only. The call site was deleted as part of NPAPI removal in [1], but this method was not. Furthermore, PPAPI Flash now uses a different code path to retrieve cookie settings (see: PepperFlashBrowserHost::GetLocalDataRestrictions).

-- ContentBrowserClient::AllowWebRTCIdentityCache

This was used to disable the Chromium implementation of WebRTC's DtlsIdentityStoreInterface, which provided caching of identities/certificates to be used for the DTLS handshake by a peer connection. This identity is no longer generated or cached by Chromium (see [1] and [2]), instead it is now generated every time by WebRTC.

[1]: https://crrev.com/385358
[2]: https://codereview.chromium.org/2033353002/
[3]: https://codereview.chromium.org/2137023002