You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Downloads are handled automatically. A default `SaveAs` file dialog provided by OS is displayed. See also the [DownloadHandler](DownloadHandler.md) wiki page.
176
173
177
174
178
-
### external_message_pump
179
-
180
-
(bool)
181
-
Default: False
182
-
183
-
EXPERIMENTAL: So far this was tested only on Linux and actually made app
184
-
significantly slower. Windows and Mac platforms were not
185
-
tested yet. Reported issue in upstream, see [Issue #246]
186
-
(https://github.com/cztomczak/cefpython/issues/246) for details.
187
-
188
-
It is recommended to use this option as a replacement for calls to
189
-
cefpython.MessageLoopWork(). CEF Python will do these calls automatically
190
-
using CEF's OnScheduleMessagePumpWork. This results in improved performance
191
-
on Windows and Mac and resolves some bugs with missing keyboard events
192
-
on these platforms. See [Issue #246]
193
-
(https://github.com/cztomczak/cefpython/issues/246) for more details.
194
-
195
-
Description from upstream CEF:
196
-
> Set to true (1) to control browser process main (UI) thread message pump
197
-
> scheduling via the CefBrowserProcessHandler::OnScheduleMessagePumpWork()
198
-
> callback. This option is recommended for use in combination with the
199
-
> CefDoMessageLoopWork() function in cases where the CEF message loop must be
200
-
> integrated into an existing application message loop (see additional
201
-
> comments and warnings on CefDoMessageLoopWork). Enabling this option is not
202
-
> recommended for most users; leave this option disabled and use either the
203
-
> CefRunMessageLoop() function or multi_threaded_message_loop if possible.
204
-
205
-
206
-
### framework_dir_path
207
-
208
-
The path to the CEF framework directory on macOS. If this value is empty
209
-
then the framework must exist at "Contents/Frameworks/Chromium Embedded
210
-
Framework.framework" in the top-level app bundle. Also configurable using
211
-
the "framework-dir-path" command-line switch.
212
-
213
-
See also [Issue #304](../../../issues/304).
214
-
215
-
216
175
### ignore_certificate_errors
217
176
218
177
(bool)
@@ -322,19 +281,6 @@ only supported on Windows.
322
281
This option is not and cannot be supported on OS-X for architectural reasons.
323
282
324
283
325
-
### net_security_expiration_enabled
326
-
327
-
(bool)
328
-
Set to true (1) to enable date-based expiration of built in network
329
-
security information (i.e. certificate transparency logs, HSTS preloading
330
-
and pinning information). Enabling this option improves network security
331
-
but may cause HTTPS load failures when using CEF binaries built more than
332
-
10 weeks in the past. See https://www.certificate-transparency.org/ and
333
-
https://www.chromium.org/hsts for details. Can be set globally using the
334
-
CefSettings.enable_net_security_expiration value.
335
-
336
-
337
-
338
284
### pack_loading_disabled
339
285
340
286
(bool)
@@ -447,7 +393,7 @@ set `unique_request_context_per_browser` to True.
447
393
448
394
In upstream CEF each request context may have separate settings like
(bool) Controls whether file URLs will have access to all URLs. Also configurable using the --allow-universal-access-from-files switch. Other similar switches are --allow-file-access and --allow-file-access-from-files.
169
168
170
169
171
-
### user_style_sheet_location
172
-
173
-
(string) Location of the user style sheet that will be used for all pages. This must be a data URL of the form `data:text/css;charset=utf-8;base64,content` where "content" is the base64 encoded contents of the CSS file. Also configurable using the "user-style-sheet-location" command-line switch.
174
-
175
-
This setting was removed in Chrome 33. Soon it will be removed from cefpython as well.
176
-
177
-
178
170
### web_security_disabled
179
171
180
172
(bool) Controls whether web security restrictions (same-origin policy) will be enforced. Disabling this setting is not recommend as it will allow risky security behavior such as cross-site scripting (XSS). Also configurable using the --disable-web-security switch.
Copy file name to clipboardExpand all lines: api/DpiAware.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Table of contents:
24
24
By default if DPI awareness is not enabled in application, then OS performs display scaling. That causes text to look blurry on high DPI displays. To resolve this you have to
25
25
call `cef.DpiAware.EnableHighDpiSupport` method. High DPI support is available only on Windows.
26
26
27
-
Enabling High DPI support in app can be done by embedding a DPI awareness xml manifest in both main executable and subprocess executable (see [Issue #112](../issues/112) comment #2), or by calling the `cef.DpiAware.EnableHighDpiSupport` method.
27
+
Enabling High DPI support in app can be done by embedding a DPI awareness xml manifest in both main executable and subprocess executable (see [Issue #112](../issues/112) comment #2), or by calling the `cef.DpiAware.EnableHighDpiSupport` method (Win7+).
28
28
29
29
## Static methods
30
30
@@ -52,7 +52,7 @@ the `GetSystemDpi` method for that.
52
52
|__Return__| void |
53
53
54
54
Calling this function will set current process and subprocesses
55
-
to be DPI aware.
55
+
to be DPI aware. This function supports only Windows 7 or newer.
56
56
57
57
Description from upstream CEF:
58
58
> Call during process startup to enable High-DPI support on Windows 7 or newer.
@@ -101,8 +101,8 @@ On Win8 this will return True if DPI awareness is set to either "System DPI awar
101
101
| --- | --- |
102
102
|__Return__| void |
103
103
104
-
Calling this method is deprecated, call instead `EnableHighDpiSupport()`.
105
-
See [Issue #358](../../../issues/358) for how the behavior changed in
106
-
latest CEF. This method now internally calls `EnableHighDpiSupport()`.
107
-
108
104
Enables DPI awareness for the running process. Embedding a DPI manifest in .exe is the prefered way, as it gives more reliable results, otherwise some display bugs may appear (discussed in the "Introduction" section on this page).
105
+
106
+
This function only sets DPI awareness for the main process.
107
+
It's recommended to embed a DPI awareness manifest in both main process
108
+
and the subprocesses (the subprocess.exe executable).
0 commit comments