1
0
mirror of https://github.com/salvadordf/CEF4Delphi.git synced 2025-06-22 22:17:48 +02:00

Update to CEF 134.3.1

This commit is contained in:
Salvador Díaz Fau
2025-03-13 11:51:28 +01:00
parent 752306b7c9
commit e223d1c0a6
55 changed files with 5848 additions and 3242 deletions

View File

@ -585,9 +585,17 @@
<td class="itemdesc"> Callback interface for ICefRequestContext.ResolveHost. </td>
</tr>
<tr class="list">
<td class="itemname">Interface&nbsp;<a class="bold" href="uCEFInterfaces.ICefPreferenceObserver.html"><code>ICefPreferenceObserver</code></a></td>
<td class="itemdesc"> Implemented by the client to observe preference changes and registered via ICefPreferenceManager.AddPreferenceObserver. The functions of this structure will be called on the browser process UI thread. </td>
</tr>
<tr class="list2">
<td class="itemname">Interface&nbsp;<a class="bold" href="uCEFInterfaces.ICefPreferenceManager.html"><code>ICefPreferenceManager</code></a></td>
<td class="itemdesc"> Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in ICefBrowserProcessHandler.OnRegisterCustomPreferences. </td>
</tr>
<tr class="list">
<td class="itemname">Interface&nbsp;<a class="bold" href="uCEFInterfaces.ICefSettingObserver.html"><code>ICefSettingObserver</code></a></td>
<td class="itemdesc"> Implemented by the client to observe content and website setting changes and registered via ICefRequestContext.AddSettingObserver. The functions of this structure will be called on the browser process UI thread. </td>
</tr>
<tr class="list2">
<td class="itemname">Interface&nbsp;<a class="bold" href="uCEFInterfaces.ICefRequestContext.html"><code>ICefRequestContext</code></a></td>
<td class="itemdesc"> A request context provides request handling for a set of related browser or URL request objects. A request context can be specified when creating a new browser via the ICefBrowserHost static factory functions or when creating a new URL request via the ICefUrlRequest static factory functions. Browser objects with different request contexts will never be hosted in the same render process. Browser objects with the same request context may or may not be hosted in the same render process depending on the process model. Browser objects created indirectly via the JavaScript window.open function or targeted links will share the same render process and the same request context as the source browser. When running in single-process mode there is only a single render process (the main process) and so all browsers created in single-process mode will share the same request context. This will be the first request context passed into a ICefBrowserHost static factory function and all other request context objects will be ignored. </td>