Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in ICefBrowserProcessHandler.OnRegisterCustomPreferences. </p>
<tdclass="itemcode"><code>class function <strong><ahref="uCEFPreferenceManager.TCefPreferenceManagerRef.html#UnWrap-Pointer-">UnWrap</a></strong>(data: Pointer): <ahref="uCEFInterfaces.ICefPreferenceManager.html">ICefPreferenceManager</a>;</code></td>
<tdclass="itemcode"><code>class function <strong><ahref="uCEFPreferenceManager.TCefPreferenceManagerRef.html#Global">Global</a></strong>: <ahref="uCEFInterfaces.ICefPreferenceManager.html">ICefPreferenceManager</a>;</code></td>
Returns the value for the preference with the specified |name|. Returns NULL if the preference does not exist. The returned object contains a copy of the underlying preference value and modifications to the returned object will not modify the underlying preference value. This function must be called on the browser process UI thread. </p>
Returns the value for the preference with the specified |name|. Returns NULL if the preference does not exist. The returned object contains a copy of the underlying preference value and modifications to the returned object will not modify the underlying preference value. This function must be called on the browser process UI thread. </p>
Returns true (1) if the preference with the specified |name| can be modified using SetPreference. As one example preferences set via the command-line usually cannot be modified. This function must be called on the browser process UI thread. </p>
Returns true (1) if the preference with the specified |name| can be modified using SetPreference. As one example preferences set via the command-line usually cannot be modified. This function must be called on the browser process UI thread. </p>
Add an observer for preference changes. |name| is the name of the preference to observe. If |name| is NULL then all preferences will be observed. Observing all preferences has performance consequences and is not recommended outside of testing scenarios. The observer will remain registered until the returned Registration object is destroyed. This function must be called on the browser process UI thread. </p>
<tdclass="itemcode"><spanid="UnWrap-Pointer-"></span><code>class function <strong>UnWrap</strong>(data: Pointer): <ahref="uCEFInterfaces.ICefPreferenceManager.html">ICefPreferenceManager</a>;</code></td>
</tr>
<tr><tdcolspan="2">
<pclass="nodescription">This item has no description.</p></td></tr>
<tdclass="itemcode"><spanid="Global"></span><code>class function <strong>Global</strong>: <ahref="uCEFInterfaces.ICefPreferenceManager.html">ICefPreferenceManager</a>;</code></td>
Returns the current Chrome Variations configuration (combination of field trials and <ahref="chrome://flags">chrome://flags</a>) as equivalent command-line switches (`–[enable|disable]-features=XXXX`, etc). These switches can be used to apply the same configuration when launching a CEF-based application. See <ahref="https://developer.chrome.com/docs/web-platform/chrome-variations">https://developer.chrome.com/docs/web-platform/chrome-variations</a> for background and details. Note that field trial tests are disabled by default in Official CEF builds (via the `disable_fieldtrial_testing_config=true (1)` GN flag). This function must be called on the browser process UI thread. </p>
Returns the current Chrome Variations configuration (combination of field trials and <ahref="chrome://flags">chrome://flags</a>) as human-readable strings. This is the human- readable equivalent of the "Active Variations" section of <ahref="chrome://version">chrome://version</a>. See <ahref="https://developer.chrome.com/docs/web-platform/chrome-variations">https://developer.chrome.com/docs/web-platform/chrome-variations</a> for background and details. Note that field trial tests are disabled by default in Official CEF builds (via the `disable_fieldtrial_testing_config=true (1)` GN flag). This function must be called on the browser process UI thread. </p>
