function LoadCEFlibrary: boolean; virtual;function GetCookiesDir(const aRootDirectory : string) : string;
Commit hash.
Cookie priority values.
Chrome toolbar types.
Docking modes supported by ICefWindow.AddOverlay.
The browser crashed. Internal use only: resume pending downloads if possible.
The file cannot be accessed due to security restrictions.
The file was blocked due to local policy.
Generic file operation failure.
The partial file didn't match the expected hash.
The directory or file name is too long.
There is not enough room on the drive.
The source and the target of the download were the same.
An attempt to check the safety of the download failed due to unexpected reasons. See http://crbug.com/153212.
The file is too large for the file system to handle.
An attempt was made to seek past the end of a file in opening a file (as part of resuming a previously interrupted download).
The file was in use. Too many files are opened at once. We have run out of memory.
The file contains a virus.
The network connection has been lost.
Generic network failure.
The network request was invalid. This may be due to the original URL or a redirected URL: - Having an unsupported scheme. - Being an invalid URL. - Being disallowed by policy.
The server has gone down.
The network operation timed out.
No interrupt reason.
The server does not have the requested data.
Server certificate problem.
The server sent fewer bytes than the content-length header. It may indicate that the connection was closed prematurely, or the Content-Length header was invalid. The download is only interrupted if strong validators are present. Otherwise, it is treated as finished.
An unexpected cross-origin redirect happened.
The server indicates that the operation has failed (generic).
Server access forbidden.
The server does not support range requests. Internal use only: must restart from the beginning.
Server didn't authorize access to resource.
Unexpected server response. This might indicate that the responding server may not be the intended server.
The user canceled the download.
The user shut down the browser. Internal use only: resume pending downloads if possible.
This severity log level causes a crash.
Used in the severity parameter in the 'cef_log' function, also known as 'CefLog' in CEF4Delphi. The log severities are used to index into the array of names, see log_severity_names. /base/allocator/partition_allocator/partition_alloc_base/logging.h /base/logging.cc
Desktop audio capture permission.
Desktop video capture permission.
Device audio capture permission.
Device video capture permission.
No permission.
Modifier values used in the Input.dispatchMouseEvent DevTools method. A number indicating which buttons are pressed on the mouse when a mouse event is triggered. Left=1, Right=2, Middle=4, Back=8, Forward=16, None=0. https://chromedevtools.github.io/devtools-protocol/tot/Input/#method-dispatchMouseEvent
Auto_detect proxy type: Auto detect proxy settings.
Direct proxy type: Never use a proxy.
Fixed_servers proxy type: Use fixed proxy servers.
Pac_script proxy type: Use a .pac proxy script.
System proxy type: Use system proxy settings.
The action is not allowed by a policy.
The process is of an unknown type.
First Chrome result code.
Last Chrome result code.
Cloud policy enrollment is failed or given up by user.
Chrome was downgraded since the last launch. Perform downgrade processing and relaunch.
Returned when the user has not yet accepted the EULA.
The GPU process exited because initialization failed.
The GPU process was terminated due to context lost.
Process hung.
Browser import hung and was killed.
Failed to install an item from the webstore when the kInstallEphemeralAppFromWebstore command line flag was present. As this flag is no longer supported, this return code should never be returned.
An invalid command line url was given.
A browser process was sandboxed. This should never happen.
Process was killed by user or system.
A bad message caused the process termination.
Machine level install exists.
A critical chrome file is missing.
Normal exit code.
For experiments this return code means that the user canceled causes the did_run "dr" signal to be reset soi this chrome run does not count as active chrome usage.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
An early startup command was executed and the browser must exit.
The browser process exited early by passing the command line to another running browser.
Chrome detected that there was a new version waiting to launch and renamed the files and launched the new version. This result code is never returned from the main process, but is instead used as a signal for early termination of browser. See `IsNormalResultCode` below.
A dummy value we should not use. See crbug.com/152285.
A dummy value we should not use. See crbug.com/152285.
Failed to pack an extension via the cmd line.
The profile was in use on another host.
Trying to restart the browser we crashed.
Windows sandbox broker terminated in shutdown.
Windows sandbox failed to forbid HCKU caching.
Windows sandbox failed to close pending handles.
Windows sandbox could not lower the token.
First Sandbox result code.
Windows sandbox failed to flush registry handles.
Windows sandbox could not set the integrity level.
Last Sandbox result code.
Windows sandbox exceeded the job memory limit.
Windows sandbox could not set the mitigation policy.
Windows sandbox failed to warmup.
Failed to make Chrome default browser (not used?).
Failed to migrate user data directory for side-by-side package support (Linux-only).
The browser process exited because system resource are exhausted. The system state can't be recovered and will be unstable.
Uninstall detected another chrome instance.
Delete profile as well during uninstall.
Failed to silently uninstall an extension.
The user changed their mind.
Command line parameter is not supported.
If CEF_SCHEME_OPTION_CORS_ENABLED is set the scheme can be sent CORS requests. This value should be set in most cases where CEF_SCHEME_OPTION_STANDARD is set.
If CEF_SCHEME_OPTION_CSP_BYPASSING is set the scheme can bypass Content- Security-Policy (CSP) checks. This value should not be set in most cases where CEF_SCHEME_OPTION_STANDARD is set.
If CEF_SCHEME_OPTION_DISPLAY_ISOLATED is set the scheme can only be displayed from other content hosted with the same scheme. For example, pages in other origins cannot create iframes or hyperlinks to URLs with the scheme. For schemes that must be accessible from other schemes don't set this, set CEF_SCHEME_OPTION_CORS_ENABLED, and use CORS "Access-Control-Allow-Origin" headers to further restrict access.
If CEF_SCHEME_OPTION_FETCH_ENABLED is set the scheme can perform Fetch API requests.
If CEF_SCHEME_OPTION_LOCAL is set the scheme will be treated with the same security rules as those applied to "file" URLs. Normal pages cannot link to or access local URLs. Also, by default, local URLs can only perform XMLHttpRequest calls to the same URL (origin + path) that originated the request. To allow XMLHttpRequest calls from a local URL to other URLs with the same origin set the CefSettings.file_access_from_file_urls_allowed value to true (1). To allow XMLHttpRequest calls from a local URL to all origins set the CefSettings.universal_access_from_file_urls_allowed value to true (1).
No options.
If CEF_SCHEME_OPTION_SECURE is set the scheme will be treated with the same security rules as those applied to "https" URLs. For example, loading this scheme from other secure schemes will not trigger mixed content warnings.
If CEF_SCHEME_OPTION_STANDARD is set the scheme will be treated as a standard scheme. Standard schemes are subject to URL canonicalization and parsing rules as defined in the Common Internet Scheme Syntax RFC 1738 Section 3.1 available at http://www.ietf.org/rfc/rfc1738.txt @@ -1054,812 +1079,812 @@
For non-standard scheme URLs only the "scheme:" component is parsed and canonicalized. The remainder of the URL will be passed to the handler as- is. For example, "scheme:///some%20text" will remain the same. Non-standard scheme URLs cannot be used as a target for form submission.
Show the window as fullscreen.
Show the window as hidden (no dock thumbnail). Only supported on MacOS..
Show the window as maximized.
Show the window as minimized.
Show the window as normal.
Represents commands available to TextField.
Values indicating what state of the touch handle is set.
Used when the shared textures are enabled.
Supported certificate status code values. See net\cert\cert_status_flags.h for more information. CERT_STATUS_NONE is new in CEF because we use an enum while cert_status_flags.h uses a typedef and static const variables.
This constant is defined by Chromium in chrome/app/main_dll_loader_win.cc It's used with SetProcessShutdownParameters to set a shutdown priority for the subprocesses. $280 is the default value for applications.
Supported context menu edit state bit flags. These constants match their equivalents in Chromium's ContextMenuDataEditFlags and should not be renumbered.
Supported context menu media state bit flags. These constants match their equivalents in Chromium's ContextMenuData::MediaFlags and should not be renumbered.
An editable element is selected.
A subframe page is selected.
A link is selected.
A media node is selected.
No node is selected.
The top page is selected.
There is a textual or mixed selection that is selected.
command_id constants declared in cef_command_ids.h and used by some callbacks in ICefCommandHandler cef_command_ids.h is generated in /include/cef_command_ids.h
Black SkColor
White SkColor
REFERENCES : ============ https://tools.ietf.org/html/rfc6749 https://tools.ietf.org/html/rfc6750 https://tools.ietf.org/html/rfc8252 https://tools.ietf.org/html/rfc6819 https://tools.ietf.org/html/rfc7636 https://tools.ietf.org/html/draft-ietf-oauth-native-apps-12 https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13 https://developers.google.com/identity/protocols/OAuth2 https://developers.google.com/identity/protocols/OAuth2InstalledApp https://developers.google.com/identity/protocols/googlescopes https://developers.google.com/identity/protocols/OpenIDConnect https://aaronparecki.com/oauth-2-simplified/ https://example-app.com/pkce
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
Print job duplex mode values.
An operation was aborted (due to user action).
Permission to access a resource, other than the network, was denied.
The IP address or port number is invalid (e.g., cannot connect to the IP address 0 or the port 0).
Returned when attempting to bind an address that is already in use.
The IP address is unreachable. This usually means that there is no route to the specified host or network.
An error adding a certificate to the OS certificate database.
The request to negotiate an alternate protocol failed.
The SSL handshake failed because of a bad or missing client certificate.
The request was blocked by the URL block list configured by the domain administrator.
The client chose to block the request.
The request was blocked by a Content Security Policy
The request was blocked by CORB or ORB.
The connection is blocked by private network access checks.
The request failed because the response was delivered along with requirements which are not met ('X-Frame-Options' and 'Content-Security-Policy' ancestor checks and 'Cross-Origin-Resource-Policy' for instance).
The IP address space of the cached remote endpoint is blocked by private network access check.
Received a challenge after the transaction has read some data, and the credentials aren't available. There isn't a way to get them at that point.
The cache found an entry with an invalid checksum. This can be returned from attempts to read from the cache. It is an internal error, returned by the SimpleCache backend, but not by any URLRequest methods or members.
The cache was unable to read a checksum record on an entry. This can be returned from attempts to read from the cache. It is an internal error, returned by the SimpleCache backend, but not by any URLRequest methods or members.
The disk cache is unable to create this entry.
The disk cache is unable to doom this entry.
Internal not-quite error code for the HTTP cache. In-memory hints suggest that the cache entry would not have been usable with the transaction's current configuration (e.g. load flags, mode, etc.)
Internal error code for the HTTP cache. The cache lock timeout has fired.
The cache does not have the requested entry.
The disk cache is unable to open this entry.
The disk cache is unable to open or create this entry.
The operation is not supported for this entry.
Multiple transactions are racing to create disk cache entries. This is an internal error returned from the HttpCache to the HttpCacheTransaction that tells the transaction to restart the entry-creation logic because the state of the cache has changed.
Unable to read from the disk cache.
Unable to write to the disk cache.
Certificate Transparency was required for this connection, but the server did not provide CT information that complied with the policy.
The server responded with a certificate that is signed by an authority we don't trust. The could mean: @@ -1870,7 +1895,7 @@
3. The server is presenting a self-signed certificate, providing no defense against active attackers (but foiling passive attackers).
The server responded with a certificate whose common name did not match the host name. This could mean: @@ -1883,19 +1908,19 @@
4. The OS has used a DNS search suffix and the server doesn't have a certificate for the abbreviated name in the address bar.
The server responded with a certificate that contains errors. This error is not recoverable.
MSDN describes this error as follows: "The SSL certificate contains errors." NOTE: It's unclear how this differs from ERR_CERT_INVALID. For consistency, use that code instead of this one from now on.
The certificate database changed in some way.
The server responded with a certificate that, by our clock, appears to either not yet be valid or to have expired. This could mean: @@ -1906,49 +1931,49 @@
3. Our clock is wrong.
The value immediately past the last certificate error code.
The server responded with a certificate that is invalid. This error is not recoverable.
MSDN describes this error as follows: "The SSL certificate is invalid."
The certificate is known to be used for interception by an entity other the device owner.
The certificate claimed DNS names that are in violation of name constraints.
The host name specified in the certificate is not unique.
The certificate has no mechanism for determining if it is revoked. In effect, this certificate cannot be revoked.
The server responded with a certificate has been revoked. We have the capability to ignore this error, but it is probably not the thing to do.
The certificate chained to a legacy Symantec root that is no longer trusted. https://g.co/chrome/symantecpkicerts
Revocation information for the security certificate for this site is not available. This could mean: @@ -1957,3825 +1982,3825 @@
2. The certificate is unrevoked, but the revocation server is busy or unavailable.
The certificate's validity period is too long.
The certificate verifier configuration changed in some way.
The server responded with a certificate that contains a weak key (e.g. a too-small RSA key).
The server responded with a certificate that is signed using a weak signature algorithm.
The request was blocked by system policy disallowing some or all cleartext requests. Used for NetworkSecurityPolicy on Android.
Server request for client certificate did not contain any types we support.
A connection timed out as a result of not receiving an ACK for data sent. This can include a FIN packet that did not get ACK'd.
A connection was closed (corresponding to a TCP FIN).
A connection attempt failed.
A connection attempt was refused.
A connection was reset (corresponding to a TCP RST).
A connection attempt timed out.
Content decoding of the response body failed.
Initializing content decoding failed.
The HTTP response body transferred fewer bytes than were advertised by the Content-Length header when the connection is closed.
The request failed because the URLRequestContext is shutting down, or has been shut down.
Certificate Transparency: Failed to parse the received consistency proof.
Certificate Transparency: Received a signed tree head whose JSON parsing was OK but was missing some of the fields.
Certificate Transparency: Received a signed tree head that failed to parse.
The compression dictionary cannot be loaded.
The scheme of the URL is disallowed.
DNS resolver received a malformed response.
DNS identified the request as disallowed for insecure connection (http/ws). Error should be handled as if an HTTP redirect was received to redirect to https or wss.
The hostname resolution of HTTPS record was expected to be resolved with alpn values of supported protocols, but did not.
All DNS requests associated with this job have been cancelled.
Suffix search list rules prevent resolution of the given host name.
When checking whether secure DNS can be used, the response returned for the requested probe record either had no answer or was invalid.
Failed to resolve the hostname of a DNS-over-HTTPS server.
DNS server failed. This error is returned for all of the following error conditions: 1 - Format error - The name server was unable to interpret the query. 2 - Server failure - The name server was unable to process this query due to a problem with the name server. 4 - Not Implemented - The name server does not support the requested kind of query. 5 - Refused - The name server refuses to perform the specified operation for policy reasons.
DNS server requires TCP
Failed to sort addresses according to RFC3484.
DNS transaction timed out.
TLS 1.3 early data was rejected by the server. This will be received before any data is returned from the socket. The request should be retried with early data disabled.
ECH was enabled, the server was unable to decrypt the encrypted ClientHello, and additionally did not present a certificate valid for the public name.
ECH was enabled, but the server was unable to decrypt the encrypted ClientHello.
The server closed the connection without sending any data.
Converting the response to target encoding failed.
Detecting the encoding of the response failed.
A generic failure occurred.
The file already exists.
The file or directory cannot be found.
Not enough room left on the disk.
The path or file name is too long.
The file is too large.
The file has a virus.
The request was blocked because of no H/2 or QUIC session.
There are too many pending DNS resolves, so a request in the queue was aborted.
A request to create an SSL tunnel connection through the HTTPS proxy received a 302 (temporary redirect) response. The response body might include a description of why the request failed.
TODO(crbug.com/40093955): This is deprecated and should not be used by new code.
HTTP_1_1_REQUIRED error code received on HTTP/2 session.
The server returned a non-2xx HTTP response code.
Note that this error is only used by certain APIs that interpret the HTTP response itself. URLRequest for instance just passes most non-2xx response back as success.
Resolving a hostname to an IP address list included the IPv4 address "127.0.53.53". This is a special IP address which ICANN has recommended to indicate there was a name collision, and alert admins to a potential problem.
CA import failed due to some other error.
CA import failed - not a CA cert.
Import failed - certificate already exists in database. Note it's a little weird this is an error but reimporting a PKCS12 is ok (no-op). That's how Mozilla does it, though.
Server certificate import failed due to some internal error.
The HTTP response body is transferred with Chunked-Encoding, but the terminating zero-length chunk was never sent when the connection is closed.
HTTP/2 headers have been received, but not all of them - status or version headers are missing, so we're expecting additional frames to complete them.
The IP address space of the remote endpoint differed from the previous observed value during the same request. Any cache entry for the affected request should be invalidated.
The server's response was insecure (e.g. there was a cert error).
There were not enough resources to complete the operation.
The Internet connection has been lost.
An argument to the function is incorrect.
Credentials could not be established during HTTP Authentication.
Error in chunked transfer encoding.
The ECHConfigList fetched over DNS cannot be parsed.
The handle or file descriptor is invalid.
The server was expected to return an HTTP/1.x response, but did not. Rather than treat it as HTTP/0.9, this error is returned.
Attempting to load an URL resulted in a redirect to an invalid URL.
The server's response was invalid.
An error occurred while handling a signed exchange.
The URL is invalid.
An error occurred while handling a Web Bundle source.
An asynchronous IO operation is not yet complete. This usually does not indicate a fatal error. Typically this error will be generated as a notification to wait for some external notification that the IO operation finally completed.
Key generation failed.
The identity used for authentication is invalid.
A mandatory proxy configuration could not be used. Currently this means that a mandatory PAC script could not be fetched, parsed or executed.
The server did not support the request method.
The environment was not set up correctly for authentication. For example, no KDC could be found or the principal is unknown.
(GSSAPI) No Kerberos credentials were available during HTTP Authentication.
The message was too large for the transport. (for example a UDP message which exceeds size threshold).
The host name could not be resolved.
An error occurred when trying to do a name resolution (DNS).
Permission to access the network was denied. This is used to distinguish errors that were most likely caused by a firewall from other access denied errors. See also ERR_ACCESS_DENIED.
The request was blocked because it originated from a frame that has disabled network access.
The network changed.
An operation could not be completed because all network IO is suspended.
No error.
The operation failed because of unimplemented functionality.
No socket buffer space is available.
An attempt to import a client certificate failed, as the user's key database lacked a corresponding private key.
No SSL protocol versions are enabled.
There are no supported proxies in the provided list.
The entry was not found in cache or other local sources, for lookups where only local sources were queried. TODO(ericorth): Consider renaming to DNS_LOCAL_MISS or something like that as the cache is not necessarily queried either.
Memory allocation failed.
No PAC URL configuration could be retrieved from DHCP. This can indicate either a failure to retrieve the DHCP configuration, or that there was no PAC URL configured in DHCP.
The evaluation of the PAC script failed.
The PAC script terminated fatally and must be reloaded.
PKCS #12 import failed due to incorrect password.
PKCS #12 import failed due to other error.
PKCS #12 import failed due to invalid/corrupt file.
PKCS #12 import failed due to invalid MAC.
PKCS #12 import failed due to unsupported features.
We've hit the max socket limit for the socket pool while preconnecting. We don't bother trying to preconnect more sockets.
Failure to export private key.
The proxy requested authentication (for tunnel establishment).
Proxy Auth Requested without a valid Client Socket Handle.
The proxy requested authentication (for tunnel establishment) with an unsupported method.
The certificate presented by the HTTPS Proxy was invalid.
Could not create a connection to the proxy server. An error occurred either in resolving its name, or in connecting a socket to it. Note that this does NOT include failures during the actual "CONNECT" method of an HTTP proxy.
HTTP_1_1_REQUIRED error code received on HTTP/2 session to proxy.
The certificate presented on a QUIC connection does not chain to a known root and the origin connected to is not on a list of domains where unknown roots are allowed.
A GOAWAY frame has been received indicating that the request has not been processed and is therefore safe to retry on a different connection.
The QUIC crypto handshake failed. This means that the server was unable to read any requests sent, so they may be resent.
There is a QUIC protocol error.
Socket ReadIfReady support is not implemented. This error should not be user visible, because the normal Read() method is used as a fallback.
The response was 416 (Requested range not satisfiable) and the server cannot satisfy the range requested.
The HTTP response was too big to drain.
The HTTP response contained multiple Content-Disposition headers.
The HTTP response contained multiple distinct Content-Length headers.
The HTTP response contained multiple Location headers.
The headers section of the response is too large.
The HTTP headers were truncated by an EOF.
Self-signed certificate generation failed.
The socket is already connected.
The socket is not connected.
Failed to set the socket's receive buffer size as requested, despite success return code from setsockopt.
Failed to set the socket's send buffer size as requested, despite success return code from setsockopt.
Failed to set the socket's receive buffer size as requested.
Failed to set the socket's send buffer size as requested.
Failed establishing a connection to the SOCKS proxy server for a target host.
The SOCKS proxy server failed establishing connection to the target host because that host is unreachable.
Decoding or encoding of compressed HTTP/2 headers failed.
The peer violated HTTP/2 flow control.
The peer sent an improperly sized HTTP/2 frame.
Transport security is inadequate for the HTTP/2 version.
HTTP/2 server didn't respond to the PING message.
There is an HTTP/2 protocol error.
Received HTTP/2 RST_STREAM frame with NO_ERROR error code. This error should be handled internally by HTTP/2 code, and should not make it above the SpdyStream layer.
HTTP/2 server refused the request without processing, and sent either a GOAWAY frame with error code NO_ERROR and Last-Stream-ID lower than the stream id corresponding to the request indicating that this request has not been processed yet, or a RST_STREAM frame with error code REFUSED_STREAM. Client MAY retry (on a different connection). See RFC7540 Section 8.1.4.
Received an HTTP/2 frame on a closed stream.
SSL peer's public key is invalid.
An SSL peer sent us a fatal bad_record_mac alert. This has been observed from servers with buggy DEFLATE support.
Failed to import a client certificate from the platform store into the SSL library.
The server requested a client certificate for SSL client authentication.
The SSL client certificate has no private key.
There were no common signature algorithms between our client certificate private key and the server's preferences.
The permission to use the SSL client certificate's private key was denied.
We were unable to sign the CertificateVerify data of an SSL client auth handshake with the client certificate's private key.
Possible causes for this include the user implicitly or explicitly denying access to the private key, the private key may not be valid for signing, the key may be relying on a cached handle which is no longer valid, or the CSP won't allow arbitrary data to be signed.
An SSL peer sent us a fatal decompression_failure alert. This typically occurs when a peer selects DEFLATE compression in the mistaken belief that it supports it.
An SSL peer sent us a fatal decrypt_error alert. This typically occurs when a peer could not correctly verify a signature (in CertificateVerify or ServerKeyExchange) or validate a Finished message.
An operation failed because the SSL handshake has not completed.
The server's certificate has a keyUsage extension incompatible with the negotiated TLS key exchange method.
The peer sent an SSL no_renegotiation alert message.
The SSL server required an unsupported cipher suite that has since been removed. This error will temporarily be signaled on a fallback for one or two releases immediately following a cipher suite's removal, after which the fallback will be removed.
The certificate didn't match the built-in public key pins for the host name. The pins are set in net/http/transport_security_state.cc and require that one of a set of public keys exist on the path from the leaf to the root.
An SSL protocol error occurred.
The server requested a renegotiation (rehandshake).
The SSL server presented a certificate which could not be decoded. This is not a certificate error code as no X509Certificate object is available. This error is fatal.
The SSL server certificate changed in a renegotiation.
The SSL server sent us a fatal unrecognized_name alert.
The client and server don't support a common SSL protocol version or cipher suite.
FLIP data received without receiving a SYN_REPLY on the stream.
The request throttler module cancelled this request to avoid DDOS.
An operation timed out.
TLS 1.3 was enabled, but a lower version was negotiated and the server returned a value indicating it supported TLS 1.3. This is part of a security check in TLS 1.3, but it may also indicate the user is behind a buggy TLS-terminating proxy which implemented TLS 1.2 incorrectly. (See https://crbug.com/boringssl/226.)
The ACCEPT_CH restart has been triggered too many times
Attempting to load an URL resulted in too many redirects.
An HTTP transaction was retried too many times due for authentication or invalid certificates. This may be due to a bug in the net stack that would otherwise infinite loop, or if the server or proxy continually requests fresh credentials or presents a fresh invalid certificate.
A Trust Tokens protocol operation-executing request failed for one of a number of reasons (precondition failure, internal error, bad response).
When handling a Trust Tokens protocol operation-executing request, the system was able to execute the request's Trust Tokens operation without sending the request to its destination: for instance, the results could have been present in a local cache (for redemption) or the operation could have been diverted to a local provider (for "platform-provided" issuance).
A tunnel connection through the proxy could not be established.
The attempt to reuse a connection to send proxy auth credentials failed before the AuthController was used to generate credentials. The caller should reuse the controller with a new connection. This error is only used internally by the network stack.
An undocumented SSPI or GSSAPI status code was returned.
An unexpected error. This may be caused by a programming mistake or an invalid assumption.
The header of dictionary compressed stream does not match the expected value.
The response was 407 (Proxy Authentication Required), yet we did not send the request to a proxy.
An unexpected, but documented, SSPI or GSSAPI status code was returned.
The scheme of the URL is unknown.
The server sent an FTP directory listing in a format we do not understand.
Attempting to load an URL with an unsafe port number. These are port numbers that correspond to services, which are not robust to spurious input that may be constructed as a result of an allowed web construct (e.g., HTTP looks a lot like SMTP, so form submission to port 25 is denied).
Attempting to load an URL resulted in an unsafe redirect (e.g., a redirect to file:// is considered unsafe).
An HTTP Authentication scheme was tried which is not supported on this machine.
The file upload failed because the file's modification time was different from the expectation.
The upload failed because the upload stream needed to be re-read, due to a retry or a redirect, but the upload stream doesn't support that operation.
Winsock sometimes reports more data written than passed. This is probably due to a broken LSP.
TLS 1.3 early data was offered, but the server responded with TLS 1.2 or earlier. This is an internal error code to account for a backwards-compatibility issue with early data and TLS 1.2. It will be received before any data is returned from the socket. The request should be retried with early data disabled.
See https://tools.ietf.org/html/rfc8446#appendix-D.3 for details.
Websocket protocol error. Indicates that we are terminating the connection due to a malformed frame or other protocol violation.
There are too many pending WebSocketJob instances, so the new job was not pushed to the queue.
When a WebSocket handshake is done successfully and the connection has been upgraded, the URLRequest is cancelled with this error code.
Content decoding failed due to the zstd window size being too big (over 8MB).
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Requires that the file exists before allowing the user to pick it.
Like Open, but selects a folder to open.
Like Open, but allows picking multiple files to open.
Allows picking a nonexistent file, and prompts to overwrite if the file already exists.
Default behavior.
This option instructs the writer that if a Binary value is encountered, the value (and key if within a dictionary) will be omitted from the output, and success will be returned. Otherwise, if a binary value is encountered, failure will be returned.
This option instructs the writer to write doubles that have no fractional part as a normal integer (i.e., without using exponential notation or appending a '.0') as long as the value is within the range of a 64-bit int.
Return a slightly nicer formatted json string (pads with whitespace to help with readability).
for InitLibLocationFromArgs
DEBUG logging.
Default logging (currently INFO logging).
Disable logging to file for all messages, and to stderr for messages with severity less than FATAL.
ERROR logging.
FATAL logging.
INFO logging.
Verbose logging.
WARNING logging.
Prepend the default list of items.
Prepend the process ID.
Prepend the thread ID.
Prepend the tickcount.
Prepend the timestamp.
Prepend no items.
Navigation.
Custom menu items originating from the renderer process.
Miscellaneous.
Spell checking word correction suggestions.
Editing.
All user-defined menu IDs should come between MENU_ID_USER_FIRST and MENU_ID_USER_LAST to avoid overlapping the Chromium and CEF ID ranges defined in the tools/gritsettings/resource_ids file.
If any of the platform IDs are not defined then we set them as 0 to avoid build errors on older Delphi versions.
Supported quick menu state bit flags.
Supported SSL version values.
Supported SSL content status flags. See content/public/common/ssl_status.h for more information.
User got to this page through a suggestion in the UI (for example, via the destinations page). Chrome style only.
Source is a subframe navigation. This is any content that is automatically loaded in a non-toplevel frame. For example, if a page consists of several frames containing ads, those ad URLs will have this transition type. The user may not even realize the content in these pages is a separate frame, so may not care about the URL.
This is a toplevel navigation. This is any content that is automatically loaded in a toplevel frame. For example, opening a tab to show the ASH screen saver, opening the devtools window, opening the NTP after the safe browsing warning, opening web-based dialog boxes are examples of AUTO_TOPLEVEL navigations. Chrome style only.
Attempted to visit a URL but was blocked.
The last transition in a redirect chain.
The beginning of a navigation chain.
Redirects caused by JavaScript or a meta refresh tag on the page.
Loaded a URL directly via CreateBrowser, LoadURL or LoadRequest.
Source is some other "explicit" navigation. This is the default value for navigations where the actual type is unknown. See also TT_DIRECT_LOAD_FLAG.
Source is a form submission by the user. NOTE: In some situations submitting a form does not result in this transition type. This can happen if the form uses a script to submit the contents.
Used the Forward or Back function to navigate among browsing history. Will be ORed to the transition type for the original load.
The transition originated from an external application; the exact definition of this is embedder dependent. Chrome style only.
User got to this page by typing in the URL bar and selecting an entry that did not look like a URL. For example, a match might have the URL of a Google search result page, but appear like "Search Google for ...". These are not quite the same as EXPLICIT navigations because the user didn't type or see the destination URL. Chrome style only. See also TT_KEYWORD.
User is navigating to the home page. Chrome style only.
Used to test whether a transition involves a redirect.
The url was generated from a replaceable keyword other than the default search provider. If the user types a keyword (which also applies to tab-to-search) in the omnibox this qualifier is applied to the transition type of the generated url. TemplateURLModel then may generate an additional visit with a transition type of TT_KEYWORD_GENERATED against the url 'http://' + keyword. For example, if you do a tab-to-search against wikipedia the generated url has a transition qualifer of TT_KEYWORD, and TemplateURLModel generates a visit for 'wikipedia.org' with a transition type of TT_KEYWORD_GENERATED. Chrome style only.
Corresponds to a visit generated for a keyword. See description of TT_KEYWORD for more details. Chrome style only.
Source is a link click or the JavaScript window.open function. This is also the default value for requests like sub-resource loads that are not navigations.
Source is a subframe navigation explicitly requested by the user that will generate new navigation entries in the back/forward list. These are probably more important than frames that were automatically loaded in the background because the user probably cares about the fact that this link was loaded.
General mask defining the bits used for the qualifiers.
Source is a "reload" of the page via the Reload function or by re-visiting the same URL. NOTE: This is distinct from the concept of whether a particular load uses "reload semantics" (i.e. bypasses cached data).
Redirects sent from the server by HTTP headers.
General mask defining the bits used for the source values.
If set user name, password, and cookies may be sent with the request, and cookies may be saved from the response.
If set the cache will not be used at all. Setting this value is equivalent to specifying the "Cache-Control: no-store" request header. Setting this value in combination with UR_FLAG_ONLY_FROM_CACHE will cause the request to fail.
Default behavior.
If set the ICefURLRequestClient.OnDownloadData method will not be called.
If set 5XX redirect errors will be propagated to the observer instead of automatically re-tried. This currently only applies for requests originated in the browser process.
If set the request will fail if it cannot be served from the cache (or some equivalent local store). Setting this value is equivalent to specifying the "Cache-Control: only-if-cached" request header. Setting this value in combination with UR_FLAG_SKIP_CACHE or UR_FLAG_DISABLE_CACHE will cause the request to fail.
If set upload progress events will be generated when a request has a body.
If set the cache will be skipped when handling the request. Setting this value is equivalent to specifying the "Cache-Control: no-cache" request header. Setting this value in combination with UR_FLAG_ONLY_FROM_CACHE will cause the request to fail.
If set 3XX responses will cause the fetch to halt immediately rather than continue through the redirect.
Don't unescape anything at all.
Don't unescape anything special, but all normal unescaping will happen. This is a placeholder and can't be combined with other flags (since it's just the absence of them). All other unescape rules imply "normal" in addition to their special meaning. Things like escaped letters, digits, and most symbols will get unescaped with this mode.
Unescapes '/' and '\\'. If these characters were unescaped, the resulting URL won't be the same as the source one. Moreover, they are dangerous to unescape in strings that will be used as file paths or names. This value should only be used when slashes don't have special meaning, like data URLs.
URL queries use "+" for space. This flag controls that replacement.
Convert %20 to spaces. In some places where we're showing URLs, we may want this. In places where the URL may be copied and pasted out, then you wouldn't want this since it might not be interpreted in one piece by other applications.
Unescapes various characters that will change the meaning of URLs, including '%', '+', '&', '#'. Does not unescape path separators. If these characters were unescaped, the resulting URL won't be the same as the source one. This flag is used when generating final output like filenames for URLs where we won't be interpreting as a URL and want to do as much unescaping as possible.
Not configurable
Not enumerable
Writeable, Enumerable, Configurable
Not writeable
Lazarus and some old Delphi versions don't have these message contants
delay in ms to enable the browser focus <summary> YouTube restrict mode. </summary> <remarks> <para><see href="https://chromium.googlesource.com/chromium/src/+/refs/tags/77.0.3865.90/chrome/common/net/safe_search_util.h">Chromium source file: /chrome/common/net/safe_search_util.h (YouTubeRestrictMode)</see></para> <para><see href="https://www.chromium.org/administrators/policy-list-3#ForceYouTubeRestrict">Chromium policy list: https://www.chromium.org/administrators/policy-list-3#ForceYouTubeRestrict</see></para> </remarks>
/include/capi/cef_command_line_capi.h
Commit hash.
/include/capi/cef_cookie_capi.h
Cookie priority values.
/include/capi/cef_crash_util.h
/include/capi/cef_file_util_capi.h
Chrome toolbar types.
/include/capi/views/cef_display_capi.h
Docking modes supported by ICefWindow.AddOverlay.
The browser crashed. Internal use only: resume pending downloads if possible.
The file cannot be accessed due to security restrictions.
The file was blocked due to local policy.
Generic file operation failure.
The partial file didn't match the expected hash.
The directory or file name is too long.
There is not enough room on the drive.
The source and the target of the download were the same.
An attempt to check the safety of the download failed due to unexpected reasons. See http://crbug.com/153212.
The file is too large for the file system to handle.
An attempt was made to seek past the end of a file in opening a file (as part of resuming a previously interrupted download).
The file was in use. Too many files are opened at once. We have run out of memory.
The file contains a virus.
The network connection has been lost.
Generic network failure.
The network request was invalid. This may be due to the original URL or a redirected URL: - Having an unsupported scheme. - Being an invalid URL. - Being disallowed by policy.
The server has gone down.
The network operation timed out.
No interrupt reason.
The server does not have the requested data.
Server certificate problem.
The server sent fewer bytes than the content-length header. It may indicate that the connection was closed prematurely, or the Content-Length header was invalid. The download is only interrupted if strong validators are present. Otherwise, it is treated as finished.
An unexpected cross-origin redirect happened.
The server indicates that the operation has failed (generic).
Server access forbidden.
The server does not support range requests. Internal use only: must restart from the beginning.
Server didn't authorize access to resource.
Unexpected server response. This might indicate that the responding server may not be the intended server.
The user canceled the download.
The user shut down the browser. Internal use only: resume pending downloads if possible.
/include/capi/cef_drag_data_capi.h
/include/internal/cef_dump_without_crashing_internal.h
/include/internal/cef_thread_internal.h
/include/internal/cef_logging_internal.h
/include/capi/cef_path_util_capi.h
********************************* ************* CAPI ************** ********************************* /include/capi/cef_app_capi.h
/include/capi/cef_ssl_info_capi.h
/ include/capi/cef_i18n_util_capi.h
/include/capi/views/cef_label_button_capi.h
/include/capi/cef_process_util_capi.h
This severity log level causes a crash.
Used in the severity parameter in the 'cef_log' function, also known as 'CefLog' in CEF4Delphi. The log severities are used to index into the array of names, see log_severity_names. /base/allocator/partition_allocator/partition_alloc_base/logging.h /base/logging.cc
Desktop audio capture permission.
Desktop video capture permission.
Device audio capture permission.
Device video capture permission.
No permission.
/include/capi/cef_media_router_capi.h
/include/capi/cef_preference_capi.h
Modifier values used in the Input.dispatchMouseEvent DevTools method. A number indicating which buttons are pressed on the mouse when a mouse event is triggered. Left=1, Right=2, Middle=4, Back=8, Forward=16, None=0. https://chromedevtools.github.io/devtools-protocol/tot/Input/#method-dispatchMouseEvent
/include/capi/cef_print_settings_capi.h
/include/capi/cef_process_message_capi.h
Auto_detect proxy type: Auto detect proxy settings.
Direct proxy type: Never use a proxy.
Fixed_servers proxy type: Use fixed proxy servers.
Pac_script proxy type: Use a .pac proxy script.
System proxy type: Use system proxy settings.
/include/capi/cef_scheme_capi.h
/include/capi/cef_request_context_capi.h
/include/capi/cef_request_capi.h
/include/capi/cef_parser_capi.h
/include/capi/cef_resource_bundle_capi.h
/include/capi/cef_response_capi.h
The action is not allowed by a policy.
The process is of an unknown type.
First Chrome result code.
Last Chrome result code.
Cloud policy enrollment is failed or given up by user.
Chrome was downgraded since the last launch. Perform downgrade processing and relaunch.
Returned when the user has not yet accepted the EULA.
The GPU process exited because initialization failed.
The GPU process was terminated due to context lost.
Process hung.
Browser import hung and was killed.
Failed to install an item from the webstore when the kInstallEphemeralAppFromWebstore command line flag was present. As this flag is no longer supported, this return code should never be returned.
An invalid command line url was given.
A browser process was sandboxed. This should never happen.
Process was killed by user or system.
A bad message caused the process termination.
Machine level install exists.
A critical chrome file is missing.
Normal exit code.
For experiments this return code means that the user canceled causes the did_run "dr" signal to be reset soi this chrome run does not count as active chrome usage.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
Generic code used to communicate some simple outcome back to the process that launched us. This is used for experiments and the actual meaning depends on the experiment.
An early startup command was executed and the browser must exit.
The browser process exited early by passing the command line to another running browser.
Chrome detected that there was a new version waiting to launch and renamed the files and launched the new version. This result code is never returned from the main process, but is instead used as a signal for early termination of browser. See `IsNormalResultCode` below.
A dummy value we should not use. See crbug.com/152285.
A dummy value we should not use. See crbug.com/152285.
Failed to pack an extension via the cmd line.
The profile was in use on another host.
Trying to restart the browser we crashed.
Windows sandbox broker terminated in shutdown.
Windows sandbox failed to forbid HCKU caching.
Windows sandbox failed to close pending handles.
Windows sandbox could not lower the token.
First Sandbox result code.
Windows sandbox failed to flush registry handles.
Windows sandbox could not set the integrity level.
Last Sandbox result code.
Windows sandbox exceeded the job memory limit.
Windows sandbox could not set the mitigation policy.
Windows sandbox failed to warmup.
Failed to make Chrome default browser (not used?).
Failed to migrate user data directory for side-by-side package support (Linux-only).
The browser process exited because system resource are exhausted. The system state can't be recovered and will be unstable.
Uninstall detected another chrome instance.
Delete profile as well during uninstall.
Failed to silently uninstall an extension.
The user changed their mind.
Command line parameter is not supported.
If CEF_SCHEME_OPTION_CORS_ENABLED is set the scheme can be sent CORS requests. This value should be set in most cases where CEF_SCHEME_OPTION_STANDARD is set.
If CEF_SCHEME_OPTION_CSP_BYPASSING is set the scheme can bypass Content- Security-Policy (CSP) checks. This value should not be set in most cases where CEF_SCHEME_OPTION_STANDARD is set.
If CEF_SCHEME_OPTION_DISPLAY_ISOLATED is set the scheme can only be displayed from other content hosted with the same scheme. For example, pages in other origins cannot create iframes or hyperlinks to URLs with the scheme. For schemes that must be accessible from other schemes don't set this, set CEF_SCHEME_OPTION_CORS_ENABLED, and use CORS "Access-Control-Allow-Origin" headers to further restrict access.
If CEF_SCHEME_OPTION_FETCH_ENABLED is set the scheme can perform Fetch API requests.
If CEF_SCHEME_OPTION_LOCAL is set the scheme will be treated with the same security rules as those applied to "file" URLs. Normal pages cannot link to or access local URLs. Also, by default, local URLs can only perform XMLHttpRequest calls to the same URL (origin + path) that originated the request. To allow XMLHttpRequest calls from a local URL to other URLs with the same origin set the CefSettings.file_access_from_file_urls_allowed value to true (1). To allow XMLHttpRequest calls from a local URL to all origins set the CefSettings.universal_access_from_file_urls_allowed value to true (1).
No options.
If CEF_SCHEME_OPTION_SECURE is set the scheme will be treated with the same security rules as those applied to "https" URLs. For example, loading this scheme from other secure schemes will not trigger mixed content warnings.
If CEF_SCHEME_OPTION_STANDARD is set the scheme will be treated as a standard scheme. Standard schemes are subject to URL canonicalization and parsing rules as defined in the Common Internet Scheme Syntax RFC 1738 Section 3.1 available at http://www.ietf.org/rfc/rfc1738.txt @@ -1907,1206 +1932,1221 @@
For non-standard scheme URLs only the "scheme:" component is parsed and canonicalized. The remainder of the URL will be passed to the handler as- is. For example, "scheme:///some%20text" will remain the same. Non-standard scheme URLs cannot be used as a target for form submission.
/include/capi/views/cef_scroll_view_capi.h
/include/capi/cef_server_capi.h
********************************* *********** INTERNAL ************ ********************************* /include/internal/cef_app_win.h
/include/capi/cef_shared_process_message_builder_capi.h
Show the window as fullscreen.
Show the window as hidden (no dock thumbnail). Only supported on MacOS..
Show the window as maximized.
Show the window as minimized.
Show the window as normal.
/include/capi/cef_stream_capi.h
/include/internal/cef_string_list.h
/include/internal/cef_string_map.h
/include/internal/cef_string_multimap.h
/include/internal/cef_string_types.h
/include/capi/cef_task_manager_capi.h
/include/capi/cef_task_capi.h
/include/capi/views/cef_textfield_capi.h
Represents commands available to TextField.
/include/capi/cef_thread_capi.h
Values indicating what state of the touch handle is set.
Used when the shared textures are enabled.
/include/internal/cef_time.h
/include/internal/cef_trace_event_internal.h
/include/capi/cef_urlrequest_capi.h
/include/capi/cef_v8_capi.h
/include/capi/cef_values_capi.h
/include/capi/cef_waitable_event_capi.h
/include/capi/views/cef_window_capi.h
/include/capi/cef_xml_reader_capi.h
/include/capi/cef_zip_reader_capi.h
Supported certificate status code values. See net\cert\cert_status_flags.h for more information. CERT_STATUS_NONE is new in CEF because we use an enum while cert_status_flags.h uses a typedef and static const variables.
Converts TCefBaseTime to TCefTime.
Converts TCefTime to TCefBaseTime.
This constant is defined by Chromium in chrome/app/main_dll_loader_win.cc It's used with SetProcessShutdownParameters to set a shutdown priority for the subprocesses. $280 is the default value for applications.
Supported context menu edit state bit flags. These constants match their equivalents in Chromium's ContextMenuDataEditFlags and should not be renumbered.
Supported context menu media state bit flags. These constants match their equivalents in Chromium's ContextMenuData::MediaFlags and should not be renumbered.
An editable element is selected.
A subframe page is selected.
A link is selected.
A media node is selected.
No node is selected.
The top page is selected.
There is a textual or mixed selection that is selected.
command_id constants declared in cef_command_ids.h and used by some callbacks in ICefCommandHandler cef_command_ids.h is generated in /include/cef_command_ids.h
Returns the absolute path version of aPath.
Simplifies a path by removing navigation elements such as "." and ".." to produce a direct, well-formed path.
Returns true if aPath is a relative path.
Determines if aPath is a valid Universal Naming Convention (UNC) path, as opposed to a path based on a drive letter.
Tests aPath to determine if it conforms to a valid URL format.
Converts a TDateTime value to TCefBaseTime.
Converts a TDateTime value to TCefTime.
Black SkColor
White SkColor
REFERENCES : ============ https://tools.ietf.org/html/rfc6749 https://tools.ietf.org/html/rfc6750 https://tools.ietf.org/html/rfc8252 https://tools.ietf.org/html/rfc6819 https://tools.ietf.org/html/rfc7636 https://tools.ietf.org/html/draft-ietf-oauth-native-apps-12 https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13 https://developers.google.com/identity/protocols/OAuth2 https://developers.google.com/identity/protocols/OAuth2InstalledApp https://developers.google.com/identity/protocols/googlescopes https://developers.google.com/identity/protocols/OpenIDConnect https://aaronparecki.com/oauth-2-simplified/ https://example-app.com/pkce
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
DOM event category flag.
Retrieve the current system time in a double type.
Converts TCefTime from a double which is the number of seconds since epoch (Jan 1, 1970). Webkit uses this format to represent time. A value of 0 means "not initialized".
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
"Verb" of a drag-and-drop operation as negotiated between the source and destination.
Print job duplex mode values.
Convert an editting command to string.
An operation was aborted (due to user action).
Permission to access a resource, other than the network, was denied.
The IP address or port number is invalid (e.g., cannot connect to the IP address 0 or the port 0).
Returned when attempting to bind an address that is already in use.
The IP address is unreachable. This usually means that there is no route to the specified host or network.
An error adding a certificate to the OS certificate database.
The request to negotiate an alternate protocol failed.
The SSL handshake failed because of a bad or missing client certificate.
The request was blocked by the URL block list configured by the domain administrator.
The client chose to block the request.
The request was blocked by a Content Security Policy
The request was blocked by CORB or ORB.
The connection is blocked by private network access checks.
The request failed because the response was delivered along with requirements which are not met ('X-Frame-Options' and 'Content-Security-Policy' ancestor checks and 'Cross-Origin-Resource-Policy' for instance).
The IP address space of the cached remote endpoint is blocked by private network access check.
Received a challenge after the transaction has read some data, and the credentials aren't available. There isn't a way to get them at that point.
The cache found an entry with an invalid checksum. This can be returned from attempts to read from the cache. It is an internal error, returned by the SimpleCache backend, but not by any URLRequest methods or members.
The cache was unable to read a checksum record on an entry. This can be returned from attempts to read from the cache. It is an internal error, returned by the SimpleCache backend, but not by any URLRequest methods or members.
The disk cache is unable to create this entry.
The disk cache is unable to doom this entry.
Internal not-quite error code for the HTTP cache. In-memory hints suggest that the cache entry would not have been usable with the transaction's current configuration (e.g. load flags, mode, etc.)
Internal error code for the HTTP cache. The cache lock timeout has fired.
The cache does not have the requested entry.
The disk cache is unable to open this entry.
The disk cache is unable to open or create this entry.
The operation is not supported for this entry.
Multiple transactions are racing to create disk cache entries. This is an internal error returned from the HttpCache to the HttpCacheTransaction that tells the transaction to restart the entry-creation logic because the state of the cache has changed.
Unable to read from the disk cache.
Unable to write to the disk cache.
Certificate Transparency was required for this connection, but the server did not provide CT information that complied with the policy.
The server responded with a certificate that is signed by an authority we don't trust. The could mean: @@ -3468,7 +3493,7 @@
3. The server is presenting a self-signed certificate, providing no defense against active attackers (but foiling passive attackers).
The server responded with a certificate whose common name did not match the host name. This could mean: @@ -3481,19 +3506,19 @@
4. The OS has used a DNS search suffix and the server doesn't have a certificate for the abbreviated name in the address bar.
The server responded with a certificate that contains errors. This error is not recoverable.
MSDN describes this error as follows: "The SSL certificate contains errors." NOTE: It's unclear how this differs from ERR_CERT_INVALID. For consistency, use that code instead of this one from now on.
The certificate database changed in some way.
The server responded with a certificate that, by our clock, appears to either not yet be valid or to have expired. This could mean: @@ -3504,49 +3529,49 @@
3. Our clock is wrong.
The value immediately past the last certificate error code.
The server responded with a certificate that is invalid. This error is not recoverable.
MSDN describes this error as follows: "The SSL certificate is invalid."
The certificate is known to be used for interception by an entity other the device owner.
The certificate claimed DNS names that are in violation of name constraints.
The host name specified in the certificate is not unique.
The certificate has no mechanism for determining if it is revoked. In effect, this certificate cannot be revoked.
The server responded with a certificate has been revoked. We have the capability to ignore this error, but it is probably not the thing to do.
The certificate chained to a legacy Symantec root that is no longer trusted. https://g.co/chrome/symantecpkicerts
Revocation information for the security certificate for this site is not available. This could mean: @@ -3555,1095 +3580,1095 @@
2. The certificate is unrevoked, but the revocation server is busy or unavailable.
The certificate's validity period is too long.
The certificate verifier configuration changed in some way.
The server responded with a certificate that contains a weak key (e.g. a too-small RSA key).
The server responded with a certificate that is signed using a weak signature algorithm.
The request was blocked by system policy disallowing some or all cleartext requests. Used for NetworkSecurityPolicy on Android.
Server request for client certificate did not contain any types we support.
A connection timed out as a result of not receiving an ACK for data sent. This can include a FIN packet that did not get ACK'd.
A connection was closed (corresponding to a TCP FIN).
A connection attempt failed.
A connection attempt was refused.
A connection was reset (corresponding to a TCP RST).
A connection attempt timed out.
Content decoding of the response body failed.
Initializing content decoding failed.
The HTTP response body transferred fewer bytes than were advertised by the Content-Length header when the connection is closed.
The request failed because the URLRequestContext is shutting down, or has been shut down.
Certificate Transparency: Failed to parse the received consistency proof.
Certificate Transparency: Received a signed tree head whose JSON parsing was OK but was missing some of the fields.
Certificate Transparency: Received a signed tree head that failed to parse.
The compression dictionary cannot be loaded.
The scheme of the URL is disallowed.
DNS resolver received a malformed response.
DNS identified the request as disallowed for insecure connection (http/ws). Error should be handled as if an HTTP redirect was received to redirect to https or wss.
The hostname resolution of HTTPS record was expected to be resolved with alpn values of supported protocols, but did not.
All DNS requests associated with this job have been cancelled.
Suffix search list rules prevent resolution of the given host name.
When checking whether secure DNS can be used, the response returned for the requested probe record either had no answer or was invalid.
Failed to resolve the hostname of a DNS-over-HTTPS server.
DNS server failed. This error is returned for all of the following error conditions: 1 - Format error - The name server was unable to interpret the query. 2 - Server failure - The name server was unable to process this query due to a problem with the name server. 4 - Not Implemented - The name server does not support the requested kind of query. 5 - Refused - The name server refuses to perform the specified operation for policy reasons.
DNS server requires TCP
Failed to sort addresses according to RFC3484.
DNS transaction timed out.
TLS 1.3 early data was rejected by the server. This will be received before any data is returned from the socket. The request should be retried with early data disabled.
ECH was enabled, the server was unable to decrypt the encrypted ClientHello, and additionally did not present a certificate valid for the public name.
ECH was enabled, but the server was unable to decrypt the encrypted ClientHello.
The server closed the connection without sending any data.
Converting the response to target encoding failed.
Detecting the encoding of the response failed.
A generic failure occurred.
The file already exists.
The file or directory cannot be found.
Not enough room left on the disk.
The path or file name is too long.
The file is too large.
The file has a virus.
The request was blocked because of no H/2 or QUIC session.
There are too many pending DNS resolves, so a request in the queue was aborted.
A request to create an SSL tunnel connection through the HTTPS proxy received a 302 (temporary redirect) response. The response body might include a description of why the request failed.
TODO(crbug.com/40093955): This is deprecated and should not be used by new code.
HTTP_1_1_REQUIRED error code received on HTTP/2 session.
The server returned a non-2xx HTTP response code.
Note that this error is only used by certain APIs that interpret the HTTP response itself. URLRequest for instance just passes most non-2xx response back as success.
Resolving a hostname to an IP address list included the IPv4 address "127.0.53.53". This is a special IP address which ICANN has recommended to indicate there was a name collision, and alert admins to a potential problem.
CA import failed due to some other error.
CA import failed - not a CA cert.
Import failed - certificate already exists in database. Note it's a little weird this is an error but reimporting a PKCS12 is ok (no-op). That's how Mozilla does it, though.
Server certificate import failed due to some internal error.
The HTTP response body is transferred with Chunked-Encoding, but the terminating zero-length chunk was never sent when the connection is closed.
HTTP/2 headers have been received, but not all of them - status or version headers are missing, so we're expecting additional frames to complete them.
The IP address space of the remote endpoint differed from the previous observed value during the same request. Any cache entry for the affected request should be invalidated.
The server's response was insecure (e.g. there was a cert error).
There were not enough resources to complete the operation.
The Internet connection has been lost.
An argument to the function is incorrect.
Credentials could not be established during HTTP Authentication.
Error in chunked transfer encoding.
The ECHConfigList fetched over DNS cannot be parsed.
The handle or file descriptor is invalid.
The server was expected to return an HTTP/1.x response, but did not. Rather than treat it as HTTP/0.9, this error is returned.
Attempting to load an URL resulted in a redirect to an invalid URL.
The server's response was invalid.
An error occurred while handling a signed exchange.
The URL is invalid.
An error occurred while handling a Web Bundle source.
An asynchronous IO operation is not yet complete. This usually does not indicate a fatal error. Typically this error will be generated as a notification to wait for some external notification that the IO operation finally completed.
Key generation failed.
The identity used for authentication is invalid.
A mandatory proxy configuration could not be used. Currently this means that a mandatory PAC script could not be fetched, parsed or executed.
The server did not support the request method.
The environment was not set up correctly for authentication. For example, no KDC could be found or the principal is unknown.
(GSSAPI) No Kerberos credentials were available during HTTP Authentication.
The message was too large for the transport. (for example a UDP message which exceeds size threshold).
The host name could not be resolved.
An error occurred when trying to do a name resolution (DNS).
Permission to access the network was denied. This is used to distinguish errors that were most likely caused by a firewall from other access denied errors. See also ERR_ACCESS_DENIED.
The request was blocked because it originated from a frame that has disabled network access.
The network changed.
An operation could not be completed because all network IO is suspended.
No error.
The operation failed because of unimplemented functionality.
No socket buffer space is available.
An attempt to import a client certificate failed, as the user's key database lacked a corresponding private key.
No SSL protocol versions are enabled.
There are no supported proxies in the provided list.
The entry was not found in cache or other local sources, for lookups where only local sources were queried. TODO(ericorth): Consider renaming to DNS_LOCAL_MISS or something like that as the cache is not necessarily queried either.
Memory allocation failed.
No PAC URL configuration could be retrieved from DHCP. This can indicate either a failure to retrieve the DHCP configuration, or that there was no PAC URL configured in DHCP.
The evaluation of the PAC script failed.
The PAC script terminated fatally and must be reloaded.
PKCS #12 import failed due to incorrect password.
PKCS #12 import failed due to other error.
PKCS #12 import failed due to invalid/corrupt file.
PKCS #12 import failed due to invalid MAC.
PKCS #12 import failed due to unsupported features.
We've hit the max socket limit for the socket pool while preconnecting. We don't bother trying to preconnect more sockets.
Failure to export private key.
The proxy requested authentication (for tunnel establishment).
Proxy Auth Requested without a valid Client Socket Handle.
The proxy requested authentication (for tunnel establishment) with an unsupported method.
The certificate presented by the HTTPS Proxy was invalid.
Could not create a connection to the proxy server. An error occurred either in resolving its name, or in connecting a socket to it. Note that this does NOT include failures during the actual "CONNECT" method of an HTTP proxy.
HTTP_1_1_REQUIRED error code received on HTTP/2 session to proxy.
The certificate presented on a QUIC connection does not chain to a known root and the origin connected to is not on a list of domains where unknown roots are allowed.
A GOAWAY frame has been received indicating that the request has not been processed and is therefore safe to retry on a different connection.
The QUIC crypto handshake failed. This means that the server was unable to read any requests sent, so they may be resent.
There is a QUIC protocol error.
Socket ReadIfReady support is not implemented. This error should not be user visible, because the normal Read() method is used as a fallback.
The response was 416 (Requested range not satisfiable) and the server cannot satisfy the range requested.
The HTTP response was too big to drain.
The HTTP response contained multiple Content-Disposition headers.
The HTTP response contained multiple distinct Content-Length headers.
The HTTP response contained multiple Location headers.
The headers section of the response is too large.
The HTTP headers were truncated by an EOF.
Self-signed certificate generation failed.
The socket is already connected.
The socket is not connected.
Failed to set the socket's receive buffer size as requested, despite success return code from setsockopt.
Failed to set the socket's send buffer size as requested, despite success return code from setsockopt.
Failed to set the socket's receive buffer size as requested.
Failed to set the socket's send buffer size as requested.
Failed establishing a connection to the SOCKS proxy server for a target host.
The SOCKS proxy server failed establishing connection to the target host because that host is unreachable.
Decoding or encoding of compressed HTTP/2 headers failed.
The peer violated HTTP/2 flow control.
The peer sent an improperly sized HTTP/2 frame.
Transport security is inadequate for the HTTP/2 version.
HTTP/2 server didn't respond to the PING message.
There is an HTTP/2 protocol error.
Received HTTP/2 RST_STREAM frame with NO_ERROR error code. This error should be handled internally by HTTP/2 code, and should not make it above the SpdyStream layer.
HTTP/2 server refused the request without processing, and sent either a GOAWAY frame with error code NO_ERROR and Last-Stream-ID lower than the stream id corresponding to the request indicating that this request has not been processed yet, or a RST_STREAM frame with error code REFUSED_STREAM. Client MAY retry (on a different connection). See RFC7540 Section 8.1.4.
Received an HTTP/2 frame on a closed stream.
SSL peer's public key is invalid.
An SSL peer sent us a fatal bad_record_mac alert. This has been observed from servers with buggy DEFLATE support.
Failed to import a client certificate from the platform store into the SSL library.
The server requested a client certificate for SSL client authentication.
The SSL client certificate has no private key.
There were no common signature algorithms between our client certificate private key and the server's preferences.
The permission to use the SSL client certificate's private key was denied.
We were unable to sign the CertificateVerify data of an SSL client auth handshake with the client certificate's private key.
Possible causes for this include the user implicitly or explicitly denying access to the private key, the private key may not be valid for signing, the key may be relying on a cached handle which is no longer valid, or the CSP won't allow arbitrary data to be signed.
An SSL peer sent us a fatal decompression_failure alert. This typically occurs when a peer selects DEFLATE compression in the mistaken belief that it supports it.
An SSL peer sent us a fatal decrypt_error alert. This typically occurs when a peer could not correctly verify a signature (in CertificateVerify or ServerKeyExchange) or validate a Finished message.
An operation failed because the SSL handshake has not completed.
The server's certificate has a keyUsage extension incompatible with the negotiated TLS key exchange method.
The peer sent an SSL no_renegotiation alert message.
The SSL server required an unsupported cipher suite that has since been removed. This error will temporarily be signaled on a fallback for one or two releases immediately following a cipher suite's removal, after which the fallback will be removed.
The certificate didn't match the built-in public key pins for the host name. The pins are set in net/http/transport_security_state.cc and require that one of a set of public keys exist on the path from the leaf to the root.
An SSL protocol error occurred.
The server requested a renegotiation (rehandshake).
The SSL server presented a certificate which could not be decoded. This is not a certificate error code as no X509Certificate object is available. This error is fatal.
The SSL server certificate changed in a renegotiation.
The SSL server sent us a fatal unrecognized_name alert.
The client and server don't support a common SSL protocol version or cipher suite.
FLIP data received without receiving a SYN_REPLY on the stream.
The request throttler module cancelled this request to avoid DDOS.
An operation timed out.
TLS 1.3 was enabled, but a lower version was negotiated and the server returned a value indicating it supported TLS 1.3. This is part of a security check in TLS 1.3, but it may also indicate the user is behind a buggy TLS-terminating proxy which implemented TLS 1.2 incorrectly. (See https://crbug.com/boringssl/226.)
The ACCEPT_CH restart has been triggered too many times
Attempting to load an URL resulted in too many redirects.
An HTTP transaction was retried too many times due for authentication or invalid certificates. This may be due to a bug in the net stack that would otherwise infinite loop, or if the server or proxy continually requests fresh credentials or presents a fresh invalid certificate.
A Trust Tokens protocol operation-executing request failed for one of a number of reasons (precondition failure, internal error, bad response).
When handling a Trust Tokens protocol operation-executing request, the system was able to execute the request's Trust Tokens operation without sending the request to its destination: for instance, the results could have been present in a local cache (for redemption) or the operation could have been diverted to a local provider (for "platform-provided" issuance).
A tunnel connection through the proxy could not be established.
The attempt to reuse a connection to send proxy auth credentials failed before the AuthController was used to generate credentials. The caller should reuse the controller with a new connection. This error is only used internally by the network stack.
An undocumented SSPI or GSSAPI status code was returned.
An unexpected error. This may be caused by a programming mistake or an invalid assumption.
The header of dictionary compressed stream does not match the expected value.
The response was 407 (Proxy Authentication Required), yet we did not send the request to a proxy.
An unexpected, but documented, SSPI or GSSAPI status code was returned.
The scheme of the URL is unknown.
The server sent an FTP directory listing in a format we do not understand.
Attempting to load an URL with an unsafe port number. These are port numbers that correspond to services, which are not robust to spurious input that may be constructed as a result of an allowed web construct (e.g., HTTP looks a lot like SMTP, so form submission to port 25 is denied).
Attempting to load an URL resulted in an unsafe redirect (e.g., a redirect to file:// is considered unsafe).
An HTTP Authentication scheme was tried which is not supported on this machine.
The file upload failed because the file's modification time was different from the expectation.
The upload failed because the upload stream needed to be re-read, due to a retry or a redirect, but the upload stream doesn't support that operation.
Winsock sometimes reports more data written than passed. This is probably due to a broken LSP.
TLS 1.3 early data was offered, but the server responded with TLS 1.2 or earlier. This is an internal error code to account for a backwards-compatibility issue with early data and TLS 1.2. It will be received before any data is returned from the socket. The request should be retried with early data disabled.
See https://tools.ietf.org/html/rfc8446#appendix-D.3 for details.
Websocket protocol error. Indicates that we are terminating the connection due to a malformed frame or other protocol violation.
There are too many pending WebSocketJob instances, so the new job was not pushed to the queue.
When a WebSocket handshake is done successfully and the connection has been upgraded, the URLRequest is cancelled with this error code.
Content decoding failed due to the zstd window size being too big (over 8MB).
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Supported event bit flag.
Requires that the file exists before allowing the user to pick it.
Like Open, but selects a folder to open.
Like Open, but allows picking multiple files to open.
Allows picking a nonexistent file, and prompts to overwrite if the file already exists.
Returns a new TCefTime with a valid time in case the original has errors.
Returns a command line switch value if it exists.
@@ -4654,367 +4679,367 @@
Retrieves the fully qualified path for the current module.
Returns the time interval between now and from_ in milliseconds. This funcion should only be used by TCEFTimerWorkScheduler.
Custom interface used to handle all the TCefApplicationCore events.
Implement this interface to receive accessibility notification when accessibility events have been registered. The functions of this interface will be called on the UI thread.
Implement this interface to provide handler implementations. Methods will be called by the process and/or thread indicated.
Implement this interface to handle audio events.
Callback interface used for asynchronous continuation of authentication requests.
All ref-counted framework interfaces must inherit from this interface.
Callback interface used to asynchronously continue a download.
Interface representing a binary value. Can be used on any process and thread.
A Layout manager that arranges child views vertically or horizontally in a side-by-side fashion with spacing around and between the child views. The child views are always sized according to their preferred size. If the host's bounds provide insufficient space, child views will be clamped. Excess space will not be distributed. Methods must be called on the browser process UI thread unless otherwise indicated.
Interface used to represent a browser. When used in the browser process the functions of this interface may be called on any thread unless otherwise indicated in the comments. When used in the render process the functions of this interface may only be called on the main thread.
Interface used to represent the browser process aspects of a browser. The functions of this interface can only be called in the browser process. They may be called on any thread in that process unless otherwise indicated in the comments.
Interface used to implement browser process callbacks. The functions of this interface will be called on the browser process main thread unless otherwise indicated.
A View hosting a ICefBrowser instance. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle BrowserView events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle all the ICefBrowserViewDelegate events.
A View representing a button. Depending on the specific type, the button could be implemented by a native control or custom rendered. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle Button events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle all the ICefButtonDelegate events.
Generic callback interface used for asynchronous continuation.
Implement this interface to provide handler implementations.
Implement this interface to handle events related to commands. The functions of this interface will be called on the UI thread.
Interface used to create and/or parse command line arguments. Arguments with "–", "-" and, on Windows, "/" prefixes are considered switches. Switches will always precede any arguments without switch prefixes. Switches can optionally have a value specified using the "=" delimiter (e.g. "-switch=value"). An argument of "–" will terminate switch parsing with all subsequent tokens, regardless of prefix, being interpreted as non-switch arguments. Switch names should be lowercase ASCII and will be converted to such if necessary. Switch values will retain the original case and UTF8 encoding. This interface can be used before cef_initialize() is called.
Generic callback interface used for asynchronous completion.
Implement this interface to handle context menu events. The functions of this interface will be called on the UI thread.
Provides information about the context menu state. The functions of this interface can only be accessed on browser process the UI thread.
Implement this interface to filter cookies that may be sent or received from resource requests. The functions of this interface will be called on the IO thread unless otherwise indicated.
Interface used for managing cookies. The functions of this interface may be called on any thread unless otherwise indicated.
Interface to implement for visiting cookie values. The functions of this interface will always be called on the UI thread.
Interface used to read data from a stream. The functions of this interface may be called on any thread.
Interface to implement to be notified of asynchronous completion via ICefCookieManager.DeleteCookies.
Callback interface for ICefBrowserHost.AddDevToolsMessageObserver. The functions of this interface will be called on the browser process UI thread.
Implement this interface to handle dialog events. The functions of this interface will be called on the browser process UI thread.
Interface representing a dictionary value. Can be used on any process and thread.
This interface typically, but not always, corresponds to a physical display connected to the system. A fake Display may exist on a headless system, or a Display may correspond to a remote, virtual display. All size and position values are in density independent pixel (DIP) coordinates unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle events related to browser display state. The functions of this interface will be called on the UI thread.
Interface used to represent a DOM document. The functions of this interface should only be called on the render process main thread thread.
Interface used to represent a DOM node. The functions of this interface should only be called on the render process main thread.
Interface to implement for visiting the DOM. The functions of this interface will be called on the render process main thread.
Interface used to handle file downloads. The functions of this interface will called on the browser process UI thread.
Callback interface for ICefBrowserHost.DownloadImage. The functions of this interface will be called on the browser process UI thread.
Interface used to represent a download item.
Callback interface used to asynchronously cancel a download.
Interface used to represent drag data. The functions of this interface may be called on any thread.
Implement this interface to handle events related to dragging. The functions of this interface will be called on the UI thread.
Implement this interface to receive notification when tracing has completed. The functions of this interface will be called on the browser process UI thread.
Callback interface for asynchronous continuation of file dialog requests.
A simple Layout that causes the associated Panel's one child to be sized to match the bounds of its parent. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle events related to find results. The functions of this interface will be called on the UI thread.
Implement this interface to handle events related to focus. The functions of this interface will be called on the UI thread.
Interface used to represent a frame in the browser window. When used in the browser process the functions of this interface may be called on any thread unless otherwise indicated in the comments. When used in the render process the functions of this interface may only be called on the main thread.
@@ -5094,4259 +5119,4259 @@
Container for a single image represented at different scale factors. All image representations should be the same size in density independent pixel (DIP) units. For example, if the image at scale factor 1.0 is 100x100 pixels then the image at scale factor 2.0 should be 200x200 pixels – both images will display with a DIP size of 100x100 units. The functions of this interface can be called on any browser process thread.
Callback interface used for asynchronous continuation of JavaScript dialog requests.
Implement this interface to handle events related to JavaScript dialogs. The functions of this interface will be called on the UI thread.
Implement this interface to handle events related to keyboard input. The functions of this interface will be called on the UI thread.
LabelButton is a button with optional text and/or icon. Methods must be called on the browser process UI thread unless otherwise indicated.
A Layout handles the sizing of the children of a Panel according to implementation-specific heuristics. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle events related to browser life span. The functions of this interface will be called on the UI thread unless otherwise indicated.
Interface representing a list value. Can be used on any process and thread.
Implement this interface to handle events related to browser load status. The functions of this interface will be called on the browser process UI thread or render process main thread (TID_RENDERER).
Callback interface used for asynchronous continuation of media access permission requests.
Implement this interface to handle events related to media access permission requests. The functions of this interface will be called on the browser process UI thread.
Implemented by the client to observe MediaRouter events and registered via ICefMediaRouter.AddObserver. The functions of this interface will be called on the browser process UI thread.
Represents the route between a media source and sink. Instances of this object are created via ICefMediaRouter.CreateRoute and retrieved via ICefMediaObserver.OnRoutes. Contains the status and metadata of a routing operation. The functions of this interface may be called on any browser process thread unless otherwise indicated.
Callback interface for ICefMediaRouter.CreateRoute. The functions of this interface will be called on the browser process UI thread.
Supports discovery of and communication with media devices on the local network via the Cast and DIAL protocols. The functions of this interface may be called on any browser process thread unless otherwise indicated.
Represents a sink to which media can be routed. Instances of this object are retrieved via ICefMediaObserver.OnSinks. The functions of this interface may be called on any browser process thread unless otherwise indicated.
Callback interface for ICefMediaSink.GetDeviceInfo. The functions of this interface will be called on the browser process UI thread.
Represents a source from which media can be routed. Instances of this object are retrieved via ICefMediaRouter.GetSource. The functions of this interface may be called on any browser process thread unless otherwise indicated.
MenuButton is a button with optional text, icon and/or menu marker that shows a menu when clicked with the left mouse button. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle MenuButton events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle all the ICefMenuButtonDelegate events.
MenuButton pressed lock is released when this object is destroyed.
Supports creation and modification of menus. See TCefMenuId for the command ids that have default implementations. All user-defined command ids should be between MENU_ID_USER_FIRST and MENU_ID_USER_LAST. The functions of this interface can only be accessed on the browser process the UI thread.
Implement this interface to handle menu model events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Interface used to represent an entry in navigation history.
Callback interface for ICefBrowserHost.GetNavigationEntries. The functions of this interface will be called on the browser process UI thread.
Controller for an overlay that contains a contents View added via ICefWindow.AddOverlayView. Methods exposed by this controller should be called in preference to functions of the same name exposed by the contents View unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
A Panel is a container in the views hierarchy that can contain other Views as children. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle Panel events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle all the ICefPanelDelegate events.
Callback interface for ICefBrowserHost.PrintToPDF. The functions of this interface will be called on the browser process UI thread.
Implement this interface to handle events related to permission requests. The functions of this interface will be called on the browser process UI thread.
Callback interface used for asynchronous continuation of permission prompts.
Interface used to represent post data for a web request. The functions of this interface may be called on any thread.
Interface used to represent a single element in the request post data. The functions of this interface may be called on any thread.
Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in ICefBrowserProcessHandler.OnRegisterCustomPreferences.
Callback interface for asynchronous continuation of print dialog requests.
Implement this interface to handle printing on Linux. Each browser will have only one print job in progress at a time. The functions of this interface will be called on the browser process UI thread.
Callback interface for asynchronous continuation of print job requests.
Interface representing print settings.
Interface representing a message. Can be used on any process and thread.
Structure the client can implement to provide a custom stream reader. The functions of this structure may be called on any thread.
Generic callback interface used for managing the lifespan of a registration.
Implement this interface to handle events when window rendering is disabled. The functions of this interface will be called on the UI thread.
Interface used to implement render process callbacks. The functions of this interface will be called on the render process main thread (TID_RENDERER) unless otherwise indicated.
Interface used to represent a web request. The functions of this interface may be called on any thread.
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.
Implement this interface to provide handler implementations. The handler instance will not be released until all objects related to the context have been destroyed.
Implement this interface to handle events related to browser requests. The functions of this interface will be called on the thread indicated.
Callback interface for ICefRequestContext.ResolveHost.
Interface used for retrieving resources from the resource bundle (*.pak) files loaded by CEF during startup or via the ICefResourceBundleHandler returned from ICefApp.GetResourceBundleHandler. See TCefSettings for additional options related to resource bundle loading. The functions of this interface may be called on any thread unless otherwise indicated.
Interface used to implement a custom resource bundle interface. See TCefSettings for additional options related to resource bundle loading. The functions of this interface may be called on multiple threads.
Interface used to implement a custom request handler interface. The functions of this interface will be called on the IO thread unless otherwise indicated.
Callback for asynchronous continuation of ICefResourceHandler.read.
Implement this interface to handle events related to browser requests. The functions of this interface will be called on the IO thread unless otherwise indicated.
Callback for asynchronous continuation of ICefResourceHandler.skip.
Interface used to represent a web response. The functions of this interface may be called on any thread.
Implement this interface to filter resource response content. The functions of this interface will be called on the browser process IO thread.
Callback interface used for continuation of custom context menu display.
Callback interface for ICefBrowserHost.RunFileDialog. The functions of this interface will be called on the browser process UI thread.
Callback interface used for continuation of custom quick menu display.
Interface that creates ICefResourceHandler instances for handling scheme requests. The functions of this interface will always be called on the IO thread.
A ScrollView will show horizontal and/or vertical scrollbars when necessary based on the size of the attached content view. Methods must be called on the browser process UI thread unless otherwise indicated.
Callback interface used to select a client certificate for authentication.
Interface representing a server that supports HTTP and WebSocket requests. Server capacity is limited and is intended to handle only a small number of simultaneous connections (e.g. for communicating between applications on localhost). The functions of this interface are safe to call from any thread in the brower process unless otherwise indicated.
Implement this interface to handle HTTP server requests. A new thread will be created for each ICefServer.CreateServer call (the "dedicated server thread"), and the functions of this interface will be called on that thread. It is therefore recommended to use a different ICefServerHandler instance for each ICefServer.CreateServer call to avoid thread safety issues in the ICefServerHandler implementation.
Interface to implement to be notified of asynchronous completion via ICefCookieManager.SetCookie.
Interface that wraps platform-dependent share memory region mapping.
Interface that builds a ICefProcessMessage containing a shared memory region. This interface is not thread-safe but may be used exclusively on a different thread from the one which constructed it.
Interface representing SSL information.
Interface representing the SSL information for a navigation entry.
Interface used to read data from a stream. The functions of this interface may be called on any thread.
Interface used to write data to a stream. The functions of this interface may be called on any thread.
Custom interface used to handle all the CEF functions related to CefStringList.
Custom interface used to handle all the CEF functions related to CefStringMap.
Custom interface used to handle all the CEF functions related to CefStringMultimap.
Implement this interface to receive string values asynchronously.
Implement this interface for asynchronous task execution. If the task is posted successfully and if the associated message loop is still running then the execute() function will be called on the target thread. If the task fails to post then the task object may be destroyed on the source thread instead of the target thread. For this reason be cautious when performing work in the task object destructor.
Interface that facilitates managing the browser-related tasks. The functions of this structure may only be called on the UI thread.
Interface that asynchronously executes tasks on the associated thread. It is safe to call the functions of this interface on any thread.
CEF maintains multiple internal threads that are used for handling different types of tasks in different processes. The TCefThreadId definitions in cef_types.h list the common CEF threads. Task runners are also available for other CEF threads as appropriate (for example, V8 WebWorker threads).
A Textfield supports editing of text. This control is custom rendered with no platform-specific code. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle Textfield events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle all the ICefTextfieldDelegate events.
A simple thread abstraction that establishes a message loop on a new thread. The consumer uses ICefTaskRunner to execute code on the thread's message loop. The thread is terminated when the ICefThread object is destroyed or stop() is called. All pending tasks queued on the thread's message loop will run to completion before the thread is terminated. cef_thread_create() can be called on any valid CEF thread in either the browser or render process. This interface should only be used for tasks that require a dedicated thread. In most cases you can post tasks to an existing CEF thread instead of creating a new one; see cef_task.h for details.
Callback structure for asynchronous handling of an unresponsive process.
Interface used to make a URL request. URL requests are not associated with a browser instance so no ICefClient callbacks will be executed. URL requests can be created on any valid CEF thread in either the browser or render process. Once created the functions of the URL request object must be accessed on the same thread that created it.
Interface that should be implemented by the ICefUrlRequest client. The functions of this interface will be called on the same thread that created the request unless otherwise documented.
Custom interface used to handle all the TCEFUrlRequestClientComponent events.
Interface that should be implemented to handle V8 accessor calls. Accessor identifiers are registered by calling ICefV8value.SetValue(). The functions of this interface will be called on the thread associated with the V8 accessor.
Callback interface that is passed to ICefV8value.CreateArrayBuffer.
Interface representing a V8 context handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefV8context.GetTaskRunner() function.
Interface representing a V8 exception. The functions of this interface may be called on any render process thread.
Interface that should be implemented to handle V8 function calls. The functions of this interface will be called on the thread associated with the V8 function.
Interface that should be implemented to handle V8 interceptor calls. The functions of this interface will be called on the thread associated with the V8 interceptor. Interceptor's named property handlers (with first argument of type CefString) are called when object is indexed by string. Indexed property handlers (with first argument of type int) are called when object is indexed by integer.
Interface representing a V8 stack frame handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Interface representing a V8 stack trace handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Interface representing a V8 value handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Interface that wraps other data value types. Complex types (binary, dictionary and list) will be referenced but not owned by this object. Can be used on any process and thread.
A View is a rectangle within the views View hierarchy. It is the base interface for all Views. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle view events. All size and position values are in density independent pixels (DIP) unless otherwise indicated. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle the ICefViewDelegate events.
WaitableEvent is a thread synchronization tool that allows one thread to wait for another thread to finish some work. This is equivalent to using a Lock+ConditionVariable to protect a simple boolean value. However, using WaitableEvent in conjunction with a Lock to wait for a more complex state change (e.g., for an item to be added to a queue) is not recommended. In that case consider using a ConditionVariable instead of a WaitableEvent. It is safe to create and/or signal a WaitableEvent from any thread. Blocking on a WaitableEvent by calling the *wait() functions is not allowed on the browser process UI or IO threads.
A Window is a top-level Window/widget in the Views hierarchy. By default it will have a non-client area with title bar, icon and buttons that supports moving and resizing. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle window events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom interface used to handle all the ICefWindowDelegate events.
Interface the client can implement to provide a custom stream writer. The functions of this interface may be called on any thread.
Interface representing a X.509 certificate.
Interface representing the issuer or subject field of an X.509 certificate.
Interface that supports the reading of XML data via the libxml streaming API. The functions of this interface should only be called on the thread that creates the object.
Interface that supports the reading of zip archives via the zlib unzip API. The functions of this interface should only be called on the thread that creates the object.
Custom interface used to handle all the TChromiumCore events.
Initialize a TCefTime variable.
Returns true if the command line switch has a "type" value.
Custom interface used to handle all the TCEFServerComponent events.
Default behavior.
This option instructs the writer that if a Binary value is encountered, the value (and key if within a dictionary) will be omitted from the output, and success will be returned. Otherwise, if a binary value is encountered, failure will be returned.
This option instructs the writer to write doubles that have no fractional part as a normal integer (i.e., without using exponential notation or appending a '.0') as long as the value is within the range of a 64-bit int.
Return a slightly nicer formatted json string (pads with whitespace to help with readability).
for InitLibLocationFromArgs
DEBUG logging.
Default logging (currently INFO logging).
Disable logging to file for all messages, and to stderr for messages with severity less than FATAL.
ERROR logging.
FATAL logging.
INFO logging.
Verbose logging.
WARNING logging.
Prepend the default list of items.
Prepend the process ID.
Prepend the thread ID.
Prepend the tickcount.
Prepend the timestamp.
Prepend no items.
Navigation.
Custom menu items originating from the renderer process.
Miscellaneous.
Spell checking word correction suggestions.
Editing.
All user-defined menu IDs should come between MENU_ID_USER_FIRST and MENU_ID_USER_LAST to avoid overlapping the Chromium and CEF ID ranges defined in the tools/gritsettings/resource_ids file.
If any of the platform IDs are not defined then we set them as 0 to avoid build errors on older Delphi versions.
Supported quick menu state bit flags.
Supported SSL version values.
Supported SSL content status flags. See content/public/common/ssl_status.h for more information.
Converts a TSystemTime value to TCefTime.
TBrowserKeyPressEvent = procedure(Sender: TObject; var Key: char; var AHandled: Boolean) of Object;
TBrowserWindow @@ -9369,384 +9394,384 @@
* Optional prevent pop-up windows by implementing Chromium.BeforePopup Chromium.OpenUrlFromTab
TBufferPanel is used by VCL and LCL applications with browsers in OSR mode to draw the browser contents. See the SimpleOSRBrowser demo for more details.
Structure containing shared texture information for the OnAcceleratedPaint callback. Resources will be released to the underlying pool for reuse when the callback returns from client code.
Implement this structure to receive accessibility notification when accessibility events have been registered. The functions of this structure will be called on the UI thread.
Describes how to interpret the alpha component of a pixel.
Status of TCefAplicationCore.
Implement this structure to provide handler implementations. Methods will be called by the process and/or thread indicated.
Main class used to simplify the CEF initialization and destruction.
Parent class of TCefApplication used to simplify the CEF initialization and destruction.
Implement this interface to provide handler implementations. Methods will be called by the process and/or thread indicated.
Implement this structure to handle audio events.
Structure representing the audio parameters for setting up the audio handler.
Callback structure used for asynchronous continuation of authentication requests.
Autoplay policy types used by TCefApplicationCore.AutoplayPolicy. See the –autoplay-policy switch.
Specifies where along the axis the CefBoxLayout child views should be laid out. Should be kept in sync with Chromium's views::LayoutAlignment type.
All ref-counted framework structures must include this structure first.
All scoped framework structures must include this structure first.
The complete list of compiler versions is here : https://docwiki.embarcadero.com/RADStudio/Athens/en/Compiler_Versions Delphi 5 Delphi 6 Delphi 7 Delphi 8 Delphi 2005 Delphi 2009 Delphi 2010 Delphi XE Delphi XE2 (First FireMonkey and 64bit compiler) Delphi XE3 Delphi XE4 Delphi XE5 Delphi XE6 Delphi XE7 Delphi XE8 Rad Studio 10 - Delphi Seattle Rad Studio 10.1 - Delphi Berlin Rad Studio 10.2 - Delphi Tokyo Rad Studio 10.3 - Delphi Rio Rad Studio 10.4 - Delphi Sydney Rad Studio 11.0 - Delphi Alexandria Rad Studio 12.0 - Delphi Athens Delphi uses MACOS for the new MacOSX and DARWIN is not defined FPC uses DARWIN for the new MacOSX and MACOS is defined for the classic Macintosh OS (System 7) We define MACOSX to avoid conflicts in both situations OS_POSIX is defined for AIX, ANDROID, ASMJS, CHROMEOS, FREEBSD, IOS, LINUX, MAC, NACL, NETBSD, OPENBSD, QNX and SOLARIS in /include/base/cef_build.h
Represents a wall clock time in UTC. Values are not guaranteed to be monotonically non-decreasing and are subject to large amounts of skew. Time is stored internally as microseconds since the Windows epoch (1601).
This is equivalent of Chromium `base::Time` (see base/time/time.h).
Values used by the battery saver mode state preference.
Callback structure used to asynchronously continue a download.
Structure representing a binary value. Can be used on any process and thread.
Class that stores a copy of the raw bitmap buffer sent by CEF in the TChromiumCore.OnPaint event.
A Layout manager that arranges child views vertically or horizontally in a side-by-side fashion with spacing around and between the child views. The child views are always sized according to their preferred size. If the host's bounds provide insufficient space, child views will be clamped. Excess space will not be distributed. Methods must be called on the browser process UI thread unless otherwise indicated.
A Layout manager that arranges child views vertically or horizontally in a side-by-side fashion with spacing around and between the child views. The child views are always sized according to their preferred size. If the host's bounds provide insufficient space, child views will be clamped. Excess space will not be distributed. Methods must be called on the browser process UI thread unless otherwise indicated.
Initialization settings. Specify NULL or 0 to get the recommended default values. Many of these and other settings can also configured using command- line switches.
Structure used to represent a browser. When used in the browser process the functions of this structure may be called on any thread unless otherwise indicated in the comments. When used in the render process the functions of this structure may only be called on the main thread.
Structure used to represent the browser process aspects of a browser. The functions of this structure can only be called in the browser process. They may be called on any thread in that process unless otherwise indicated in the comments.
Used by TCefBrowserNavigationTask to navigate in the right CEF thread.
Structure used to implement browser process callbacks. The functions of this structure will be called on the browser process main thread unless otherwise indicated.
Browser initialization settings. Specify NULL or 0 to get the recommended default values. The consequences of using custom values may not be well tested. Many of these and other settings can also configured using command- line switches.
A View hosting a ICefBrowser instance. Methods must be called on the browser process UI thread unless otherwise indicated.
Component hosting a ICefBrowserView instance.
Implement this structure to handle BrowserView events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle BrowserView events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
A View hosting a ICefBrowser instance. Methods must be called on the browser process UI thread unless otherwise indicated.
A View representing a button. Depending on the specific type, the button could be implemented by a native control or custom rendered. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle Button events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle Button events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
A View representing a button. Depending on the specific type, the button could be implemented by a native control or custom rendered. Methods must be called on the browser process UI thread unless otherwise indicated.
Specifies the button display state.
Generic callback structure used for asynchronous continuation.
Supported certificate status code values. See net\cert\cert_status_flags.h for more information. CERT_STATUS_NONE is new in CEF because we use an enum while cert_status_flags.h uses a typedef and static const variables.
Enumerates the various representations of the ordering of audio channels. Must be kept synchronized with media::ChannelLayout from Chromium. See media\base\channel_layout.h
Chrome page action icon types. Should be kept in sync with Chromium's PageActionIconType type.
Chrome toolbar button types. Should be kept in sync with CEF's internal ToolbarButtonType type.
Chrome toolbar types.
Custom class used to execute CEF tasks with a TChromiumCore component.
Storage types used by the Storage.clearDataForOrigin DevTools method in TChromiumCore.ClearDataForOrigin.
Implement this structure to provide handler implementations.
@@ -9761,587 +9786,587 @@
32-bit ARGB color value, not premultiplied. The color components are always in a known order. Equivalent to the SkColor type.
Print job color mode values.
Describes how to interpret the components of a pixel.
Specifies the color variants supported by ICefRequestContext.SetChromeThemeColor.
Flags used to customize the behavior of CefURLRequest.
Implement this structure to handle events related to commands. The functions of this structure will be called on the UI thread.
Structure used to create and/or parse command line arguments. Arguments with "–", "-" and, on Windows, "/" prefixes are considered switches. Switches will always precede any arguments without switch prefixes. Switches can optionally have a value specified using the "=" delimiter (e.g. "-switch=value"). An argument of "–" will terminate switch parsing with all subsequent tokens, regardless of prefix, being interpreted as non-switch arguments. Switch names should be lowercase ASCII and will be converted to such if necessary. Switch values will retain the original case and UTF8 encoding. This structure can be used before cef_initialize() is called.
Generic callback structure used for asynchronous completion.
Class used to keep a list of valid custom component IDs for any component that handles a CEF Task event.
Structure representing IME composition underline information. This is a thin wrapper around Blink's WebCompositionUnderline class and should be kept in sync with that.
Composition underline style.
Supported content setting types. Some types are platform-specific or only supported with Chrome style. Should be kept in sync with Chromium's ContentSettingsType type.
Supported content setting values. Should be kept in sync with Chromium's ContentSetting type.
Supported context menu edit state bit flags. These constants match their equivalents in Chromium's ContextMenuDataEditFlags and should not be renumbered.
Implement this structure to handle context menu events. The functions of this structure will be called on the UI thread.
Supported context menu media state bit flags. These constants match their equivalents in Chromium's ContextMenuData::MediaFlags and should not be renumbered.
Supported context menu media types. These constants match their equivalents in Chromium's ContextMenuDataMediaType and should not be renumbered.
Provides information about the context menu state. The functions of this structure can only be accessed on browser process the UI thread.
Supported context menu type flags.
Cookie information.
Implement this structure to filter cookies that may be sent or received from resource requests. The functions of this structure will be called on the IO thread unless otherwise indicated.
Structure used for managing cookies. The functions of this structure may be called on any thread unless otherwise indicated.
Used in TChromium preferences to allow or block cookies.
Cookie priority values.
Cookie same site values.
Structure to implement for visiting cookie values. The functions of this structure will always be called on the UI thread.
Native Cursor handle.
Structure representing cursor information. |buffer| will be |size.width|*|size.height|*4 bytes in size and represents a BGRA image with an upper-left origin.
Cursor type values.
Array of byte. Needed only for backwards compatibility with old Delphi versions.
Custom array of int64.
CEF string maps are a set of key/value string pairs.
CEF string maps are a set of key/value string pairs.
CEF string multimaps are a set of key/value string pairs. More than one value can be assigned to a single key.
Structure to implement to be notified of asynchronous completion via ICefCookieManager.DeleteCookies().
Callback structure for ICefBrowserHost.AddDevToolsMessageObserver. The functions of this structure will be called on the browser process UI thread.
Implement this structure to handle dialog events. The functions of this structure will be called on the browser process UI thread.
Used by TCEFFileDialogInfo.
Structure representing a dictionary value. Can be used on any process and thread.
This structure typically, but not always, corresponds to a physical display connected to the system. A fake Display may exist on a headless system, or a Display may correspond to a remote, virtual display. All size and position values are in density independent pixel (DIP) coordinates unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle events related to browser display state. The functions of this structure will be called on the UI thread.
Event handler related to browser display state. The functions of this interface will be called on the UI thread.
This class typically, but not always, corresponds to a physical display connected to the system. A fake Display may exist on a headless system, or a Display may correspond to a remote, virtual display. All size and position values are in density independent pixel (DIP) coordinates unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Docking modes supported by ICefWindow.AddOverlay.
Structure used to represent a DOM document. The functions of this structure should only be called on the render process main thread thread.
DOM document types.
DOM event category flags.
DOM event processing phases.
DOM form control types. Should be kept in sync with Chromium's blink::mojom::FormControlType type.
Structure used to represent a DOM node. The functions of this structure should only be called on the render process main thread.
DOM node types.
Structure to implement for visiting the DOM. The functions of this structure will be called on the render process main thread.
Structure used to handle file downloads. The functions of this structure will called on the browser process UI thread.
Callback structure for ICefBrowserHost.DownloadImage. The functions of this structure will be called on the browser process UI thread.
Download interrupt reasons. Should be kept in sync with Chromium's download::DownloadInterruptReason type.
Structure used to represent a download item.
Callback structure used to asynchronously cancel a download.
Structure used to represent drag data. The functions of this structure may be called on any thread.
Structure representing a draggable region.
Implement this structure to handle events related to dragging. The functions of this structure will be called on the UI thread.
"Verb" of a drag-and-drop operation as negotiated between the source and destination. These constants match their equivalents in WebCore's DragActions.h and should not be renumbered.
Print job duplex mode values.
Blink editing commands used by the "Input.dispatchKeyEvent" DevTools method.
Implement this structure to receive notification when tracing has completed. The functions of this structure will be called on the browser process UI thread.
* ******************************************* **** Callback procedures and functions **** ******************************************* *
Supported error code values.
@@ -10360,187 +10385,187 @@ Ranges:
Supported event bit flags.
Native event handle.
Callback structure for asynchronous continuation of file dialog requests.
Supported file dialog modes.
A simple Layout that causes the associated Panel's one child to be sized to match the bounds of its parent. Methods must be called on the browser process UI thread unless otherwise indicated.
A simple Layout that causes the associated Panel's one child to be sized to match the bounds of its parent. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle events related to find results. The functions of this structure will be called on the UI thread.
Implement this structure to handle events related to focus. The functions of this structure will be called on the UI thread.
Focus sources.
Structure used to represent a frame in the browser window. When used in the browser process the functions of this structure may be called on any thread unless otherwise indicated in the comments. When used in the render process the functions of this structure may only be called on the main thread.
Implement this STRUCTURE to handle events related to ICefFrame life span. The order of callbacks is: @@ -10563,1057 +10588,1057 @@ Ranges:
The functions of this interface will be called on the UI thread unless otherwise indicated.
Specifies the gesture commands.
Values used by the high efficiency mode state preference.
Specifies the horizontal text alignment mode.
Container for a single image represented at different scale factors. All image representations should be the same size in density independent pixel (DIP) units. For example, if the image at scale factor 1.0 is 100x100 pixels then the image at scale factor 2.0 should be 200x200 pixels – both images will display with a DIP size of 100x100 units. The functions of this structure can be called on any browser process thread.
Structure representing insets.
Callback structure used for asynchronous continuation of JavaScript dialog requests.
Implement this structure to handle events related to JavaScript dialogs. The functions of this structure will be called on the UI thread.
Supported JavaScript dialog types.
Options that can be passed to CefParseJSON.
Options that can be passed to CefWriteJSON.
Implement this structure to handle events related to keyboard input. The functions of this structure will be called on the UI thread.
Structure representing keyboard event information.
Notification that a character was typed. Use this for text input. Key down events may generate 0, 1, or more than one character event depending on the key, locale, and operating system.
Key location value used in the TChromiumCore.dispatchKeyEvent DevTools method.
LabelButton is a button with optional text and/or icon. Methods must be called on the browser process UI thread unless otherwise indicated.
LabelButton is a button with optional text and/or icon. Methods must be called on the browser process UI thread unless otherwise indicated.
A Layout handles the sizing of the children of a Panel according to implementation-specific heuristics. Methods must be called on the browser process UI thread unless otherwise indicated.
A Layout handles the sizing of the children of a Panel according to implementation-specific heuristics. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle events related to browser life span. The functions of this structure will be called on the UI thread unless otherwise indicated.
TCEFLinkedWinControlBase is a custom TWinControl to host the child controls created by the web browser to show the web contents and it's linked to the TChromium instance that handles that web browser. TCEFLinkedWinControlBase is the parent class of TChromiumWindow, TBrowserWindow and TCEFLinkedWindowParent.
This component can be used by VCL and LCL applications. It has the same purpose as TCEFWindowParent but it has a Chromium property to link it directly to a TChromium component. TCEFLinkedWindowParent resizes the child controls created by CEF for browsers in normal mode and sets the browser focus using the linked TChromium component. TCEFWindowParent and TCEFLinkedWindowParent work fine in Windows and you can used any of them but you can't use TCEFWindowParent in Linux or MacOS.
Linux window properties, such as X11's WM_CLASS or Wayland's app_id. Those are passed to CefWindowDelegate, so the client can set them for the CefWindow's top-level. Thus, allowing window managers to correctly display the application's information (e.g., icons).
Structure representing a list value. Can be used on any process and thread.
Implement this structure to handle events related to browser load status. The functions of this structure will be called on the browser process UI thread or render process main thread (TID_RENDERER).
Log items prepended to each log line.
Log severity levels.
Structure representing CefExecuteProcess arguments.
Custom class used to execute CEF tasks with CEF4Delphi components.
Callback structure used for asynchronous continuation of media access permission requests.
Implement this structure to handle events related to media access permission requests. The functions of this structure will be called on the browser process UI thread.
Media access permissions used by OnRequestMediaAccessPermission.
Implemented by the client to observe MediaRouter events and registered via ICefMediaRouter.AddObserver. The functions of this structure will be called on the browser process UI thread.
Represents the route between a media source and sink. Instances of this object are created via ICefMediaRouter.CreateRoute and retrieved via ICefMediaObserver.OnRoutes. Contains the status and metadata of a routing operation. The functions of this structure may be called on any browser process thread unless otherwise indicated.
Connection state for a MediaRoute object.
Callback structure for ICefMediaRouter.CreateRoute. The functions of this structure will be called on the browser process UI thread.
Custom record with media route information.
Supports discovery of and communication with media devices on the local network via the Cast and DIAL protocols. The functions of this structure may be called on any browser process thread unless otherwise indicated.
Result codes for ICefMediaRouter.CreateRoute. Should be kept in sync with Chromium's media_router::mojom::RouteRequestResultCode type.
Represents a sink to which media can be routed. Instances of this object are retrieved via ICefMediaObserver.OnSinks. The functions of this structure may be called on any browser process thread unless otherwise indicated.
Device information for a MediaSink object. handler.
Callback structure for ICefMediaSink.GetDeviceInfo. The functions of this structure will be called on the browser process UI thread.
Icon types for a MediaSink object. Should be kept in sync with Chromium's media_router::SinkIconType type.
Custom record with media sink information.
Represents a source from which media can be routed. Instances of this object are retrieved via ICefMediaRouter.GetSource. The functions of this structure may be called on any browser process thread unless otherwise indicated.
Custom record with media source information.
Used by TCefMediaSinkInfo and TCefMediaSourceInfo.
Specifies how a menu will be anchored for non-RTL languages. The opposite position will be used for RTL languages.
MenuButton is a button with optional text, icon and/or menu marker that shows a menu when clicked with the left mouse button. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle MenuButton events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle MenuButton events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
MenuButton pressed lock is released when this object is destroyed.
MenuButton pressed lock is released when this object is destroyed.
MenuButton is a button with optional text, icon and/or menu marker that shows a menu when clicked with the left mouse button. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Supported color types for menu items.
Supported menu IDs. Non-English translations can be provided for the IDS_MENU_* strings in ICefResourceBundleHandler.GetLocalizedString().
Supported menu item types.
Supports creation and modification of menus. See TCefMenuId (cef_menu_id_t) for the command ids that have default implementations. All user-defined command ids should be between MENU_ID_USER_FIRST and MENU_ID_USER_LAST. The functions of this structure can only be accessed on the browser process the UI thread.
Implement this structure to handle menu model events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Flags used to customize the behavior of CefURLRequest.
Mouse button types.
Structure representing mouse event information.
Structure used to represent an entry in navigation history.
Callback structure for ICefBrowserHost.GetNavigationEntries. The functions of this structure will be called on the browser process UI thread.
Navigation types.
Values used by the –net-log-capture-mode command line switch. Sets the granularity of events to capture in the network log.
Class used to handle the IME window.
Controller for an overlay that contains a contents View added via ICefWindow.AddOverlayView. Methods exposed by this controller should be called in preference to functions of the same name exposed by the contents View unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Controller for an overlay that contains a contents View added via ICefWindow.AddOverlayView. Methods exposed by this controller should be called in preference to functions of the same name exposed by the contents View unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Paint element types.
A Panel is a container in the views hierarchy that can contain other Views as children. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle Panel events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle Panel events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
A Panel is a container in the views hierarchy that can contain other Views as children. Methods must be called on the browser process UI thread unless otherwise indicated.
Process termination status values.
Callback structure for ICefBrowserHost.PrintToPDF. The functions of this structure will be called on the browser process UI thread.
Margin type for PDF printing.
Structure representing PDF print settings. These values match the parameters supported by the DevTools Page.printToPDF function. See https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-printToPDF
Implement this structure to handle events related to permission requests. The functions of this structure will be called on the browser process UI thread.
Callback structure used for asynchronous continuation of permission prompts.
Permission request results.
Permission types used with OnShowPermissionPrompt. Some types are platform-specific or only supported with Chrome style. Should be kept in sync with Chromium's permissions::RequestType type.
Platform thread handle.
Platform thread ID.
Structure representing a point.
The device type that caused the event.
Popup window features.
Structure used to represent post data for a web request. The functions of this structure may be called on any thread.
Structure used to represent a single element in the request post data. The functions of this structure may be called on any thread.
Post data elements may represent either bytes or files.
Manage access to preferences. Many built-in preferences are registered by Chromium. Custom preferences can be registered in ICefBrowserProcessHandler.OnRegisterCustomPreferences.
Structure that manages custom preference registrations.
Class that manages custom preference registrations.
Preferences type passed to ICefBrowserProcessHandler.OnRegisterCustomPreferences.
Callback structure for asynchronous continuation of print dialog requests.
Implement this structure to handle printing on Linux. Each browser will have only one print job in progress at a time. The functions of this structure will be called on the browser process UI thread.
Callback structure for asynchronous continuation of print job requests.
Structure representing print settings.
Existing process IDs.
Structure representing a message. Can be used on any process and thread.
Sub-process types of Chromium.
Supported proxy schemes in Chromium.
Supported quick menu state bit flags.
Structure representing a range.
Structure the client can implement to provide a custom stream reader. The functions of this structure may be called on any thread.
Structure representing a rectangle.
Policy for how the Referrer HTTP header value will be sent during navigation. If the `–no-referrers` command-line flag is specified then the policy value will be ignored and the Referrer value will never be sent. Must be kept synchronized with net::URLRequest::ReferrerPolicy from Chromium.
Generic callback structure used for managing the lifespan of a registration.
Implement this structure to handle events when window rendering is disabled. The functions of this structure will be called on the UI thread.
Structure used to implement render process callbacks. The functions of this structure will be called on the render process main thread (TID_RENDERER) unless otherwise indicated.
Structure used to represent a web request. The functions of this structure may be called on any thread.
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.
Implement this structure to provide handler implementations. The handler instance will not be released until all objects related to the context have been destroyed.
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 cef_browser_host_t static factory functions or when creating a new URL request via the cef_urlrequest_t 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 cef_browser_host_t static factory function and all other request context objects will be ignored.
Request context initialization settings. Specify NULL or 0 to get the recommended default values.
Implement this structure to handle events related to browser requests. The functions of this structure will be called on the thread indicated.
Callback structure for ICefRequestContext.ResolveHost.
Structure used for retrieving resources from the resource bundle (*.pak) files loaded by CEF during startup or via the ICefResourceBundleHandler returned from ICefApp.GetResourceBundleHandler. See TCefSettings for additional options related to resource bundle loading. The functions of this structure may be called on any thread unless otherwise indicated.
Structure used to implement a custom resource bundle structure. See TCefSettings for additional options related to resource bundle loading. The functions of this structure may be called on multiple threads.
Structure used to implement a custom request handler structure. The functions of this structure will be called on the IO thread unless otherwise indicated.
Callback for asynchronous continuation of ICefResourceHandler.read().
Implement this structure to handle events related to browser requests. The functions of this structure will be called on the IO thread unless otherwise indicated.
Callback for asynchronous continuation of ICefResourceHandler.skip().
Resource type for a request. These constants match their equivalents in Chromium's ResourceType and should not be renumbered.
Structure used to represent a web response. The functions of this structure may be called on any thread.
Implement this structure to filter resource response content. The functions of this structure will be called on the browser process IO thread.
Owned class implementing a resource filter.
Reference class implementing a resource filter.
Return values for ICefResponseFilter.Filter().
Process result codes. This is not a comprehensive list, as result codes might also include platform-specific crash values (Posix signal or Windows hardware exception), or internal-only implementation values.
Return value types.
Callback structure used for continuation of custom context menu display.
Callback structure for ICefBrowserHost.RunFileDialog. The functions of this structure will be called on the browser process UI thread.
Callback structure used for continuation of custom quick menu display.
@@ -11624,899 +11649,899 @@ Ranges:
Supported UI scale factors for the platform. SCALE_FACTOR_NONE is used for density independent resources such as string, html/js files or an image that can be used for any scale factors (such as wallpapers).
Structure that creates ICefResourceHandler instances for handling scheme requests. The functions of this structure will always be called on the IO thread.
Class that creates ICefResourceHandler instances for handling scheme requests.
Configuration options for registering a custom scheme. These values are used when calling AddCustomScheme.
Structure that manages custom scheme registrations.
Class that manages custom scheme registrations.
Screen information used when window rendering is disabled. This structure is passed as a parameter to ICefRenderHandler.GetScreenInfo and should be filled in by the client.
A ScrollView will show horizontal and/or vertical scrollbars when necessary based on the size of the attached content view. Methods must be called on the browser process UI thread unless otherwise indicated.
A ScrollView will show horizontal and/or vertical scrollbars when necessary based on the size of the attached content view. Methods must be called on the browser process UI thread unless otherwise indicated.
Callback structure used to select a client certificate for authentication.
TCEFSentinel is used as a timer that checks the number of running CEF processes when you close all browsers before shutdown. This component is only used as a last resort when there's an unresolved shutdown issue in CEF or CEF4Delphi that generates exceptions when the application is closed.
Structure representing a server that supports HTTP and WebSocket requests. Server capacity is limited and is intended to handle only a small number of simultaneous connections (e.g. for communicating between applications on localhost). The functions of this structure are safe to call from any thread in the brower process unless otherwise indicated.
The TCEFServerComponent class puts together all CEF server procedures, functions, properties and events in one place.
Implement this structure to handle HTTP server requests. A new thread will be created for each ICefServer.CreateServer call (the "dedicated server thread"), and the functions of this structure will be called on that thread. It is therefore recommended to use a different ICefServerHandler instance for each ICefServer.CreateServer call to avoid thread safety issues in the ICefServerHandler implementation.
Structure to implement to be notified of asynchronous completion via ICefCookieManager.SetCookie().
Initialization settings. Specify NULL or 0 to get the recommended default values. Many of these and other settings can also configured using command- line switches.
Structure that wraps platform-dependent share memory region mapping.
Structure that builds a ICefProcessMessage containing a shared memory region. This structure is not thread-safe but may be used exclusively on a different thread from the one which constructed it.
Native texture handle.
Show states supported by ICefWindowDelegate.GetInitialShowState.
Mouse button in the TChromiumCore.SimulateMouseEvent function.
Type of mouse event in the TChromiumCore.SimulateMouseEvent function.
Pointer type in the TChromiumCore.SimulateMouseEvent function.
Type of touch event in the TChromiumCore.SimulateTouchEvent function.
Structure representing a simulated touch point.
Structure representing a size.
Supported SSL content status flags. See content/public/common/ssl_status.h for more information.
Structure representing SSL information.
Structure representing the SSL information for a navigation entry.
Supported SSL version values.
Represents the state of a setting.
Storage types.
Structure used to read data from a stream. The functions of this structure may be called on any thread.
Structure used to write data to a stream. The functions of this structure may be called on any thread.
String record used by the CEF C API. The CEF interface is built with the UTF16 string type as the default.
CEF string maps are a set of key/value string pairs.
CEF string maps are a set of key/value string pairs.
CEF string multimaps are a set of key/value string pairs. More than one value can be assigned to a single key.
CEF utf16 string type definition. Whomever allocates |str| is responsible for providing an appropriate |dtor| implementation that will free the string in the same memory space. When reusing an existing string structure make sure to call |dtor| for the old value before assigning new |str| and |dtor| values. Static strings will have a NULL |dtor| value. Using the below functions if you want this managed for you.
CEF utf8 string type definition. Whomever allocates |str| is responsible for providing an appropriate |dtor| implementation that will free the string in the same memory space. When reusing an existing string structure make sure to call |dtor| for the old value before assigning new |str| and |dtor| values. Static strings will have a NULL |dtor| value. Using the below functions if you want this managed for you.
Implement this structure to receive string values asynchronously.
CEF wide string type definition. Whomever allocates |str| is responsible for providing an appropriate |dtor| implementation that will free the string in the same memory space. When reusing an existing string structure make sure to call |dtor| for the old value before assigning new |str| and |dtor| values. Static strings will have a NULL |dtor| value. Using the below functions if you want this managed for you.
Implement this structure for asynchronous task execution. If the task is posted successfully and if the associated message loop is still running then the execute() function will be called on the target thread. If the task fails to post then the task object may be destroyed on the source thread instead of the target thread. For this reason be cautious when performing work in the task object destructor.
Structure representing task information provided by ICefTaskManager.
Structure that facilitates managing the browser-related tasks. The functions of this structure may only be called on the UI thread.
Class that facilitates managing the browser-related tasks.
Structure that asynchronously executes tasks on the associated thread. It is safe to call the functions of this structure on any thread.
CEF maintains multiple internal threads that are used for handling different types of tasks in different processes. The TCefThreadId definitions in cef_types.h list the common CEF threads. Task runners are also available for other CEF threads as appropriate (for example, V8 WebWorker threads).
Specifies the task type variants supported by CefTaskManager. Should be kept in sync with Chromium's task_manager::Task::Type type.
Process termination status values.
Specifies the gesture commands.
A Textfield supports editing of text. This control is custom rendered with no platform-specific code. Methods must be called on the browser process UI thread unless otherwise indicated.
Represents commands available to TextField.
Implement this structure to handle Textfield events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle Textfield events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
A Textfield supports editing of text. This control is custom rendered with no platform-specific code. Methods must be called on the browser process UI thread unless otherwise indicated.
Input mode of a virtual keyboard. These constants match their equivalents in Chromium's text_input_mode.h and should not be renumbered. See https://html.spec.whatwg.org/#input-modalities:-the-inputmode-attribute
Text style types. Should be kepy in sync with gfx::TextStyle.
A simple thread abstraction that establishes a message loop on a new thread. The consumer uses ICefTaskRunner to execute code on the thread's message loop. The thread is terminated when the ICefThread object is destroyed or stop() is called. All pending tasks queued on the thread's message loop will run to completion before the thread is terminated. cef_thread_create() can be called on any valid CEF thread in either the browser or render process. This structure should only be used for tasks that require a dedicated thread. In most cases you can post tasks to an existing CEF thread instead of creating a new one; see cef_task.h for details.
Existing thread IDs.
Thread priority values listed in increasing order of importance.
Time information. Values should always be in UTC.
Touch points states types.
Structure representing touch event information.
Touch handle state.
Values indicating what state of the touch handle is set.
Transition type for a request. Made up of one source value and 0 or more qualifiers.
Color mode in UI for platforms that support it.
Callback structure for asynchronous handling of an unresponsive process.
URI unescape rules passed to CefURIDecode().
URL component parts.
Structure used to make a URL request. URL requests are not associated with a browser instance so no ICefClient callbacks will be executed. URL requests can be created on any valid CEF thread in either the browser or render process. Once created the functions of the URL request object must be accessed on the same thread that created it.
Structure that should be implemented by the ICefUrlRequest client. The functions of this structure will be called on the same thread that created the request unless otherwise documented.
The TCEFUrlRequestClientComponent class puts together all CEF URL request procedures, functions, properties and events in one place.
Custom class used to execute CEF tasks with a TCEFUrlRequestClientComponent component.
Flags used to customize the behavior of CefURLRequest.
Flags that represent CefURLRequest status.
Structure that should be implemented to handle V8 accessor calls. Accessor identifiers are registered by calling ICefv8value.SetValue(). The functions of this structure will be called on the thread associated with the V8 accessor.
Callback structure that is passed to ICefv8value.CreateArrayBuffer.
Structure representing a V8 context handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Structure representing a V8 exception. The functions of this structure may be called on any render process thread.
Structure that should be implemented to handle V8 function calls. The functions of this structure will be called on the thread associated with the V8 function.
Structure that should be implemented to handle V8 interceptor calls. The functions of this structure will be called on the thread associated with the V8 interceptor. Interceptor's named property handlers (with first argument of type CefString) are called when object is indexed by string. Indexed property handlers (with first argument of type int) are called when object is indexed by integer.
V8 property attribute values.
Structure representing a V8 stack frame handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Structure representing a V8 stack trace handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Structure representing a V8 value handle. V8 handles can only be accessed from the thread on which they are created. Valid threads for creating a V8 handle include the render process main thread (TID_RENDERER) and WebWorker threads. A task runner for posting tasks on the associated thread can be retrieved via the ICefv8context.GetTaskRunner() function.
Structure that wraps other data value types. Complex types (binary, dictionary and list) will be referenced but not owned by this object. Can be used on any process and thread.
Supported value types.
A View is a rectangle within the views View hierarchy. It is the base structure for all Views. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle view events. All size and position values are in density independent pixels (DIP) unless otherwise indicated. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle view events. All size and position values are in density independent pixels (DIP) unless otherwise indicated. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Custom class used to execute CEF tasks with a TCEFViewComponent component.
A View is a rectangle within the views View hierarchy. It is the base interface for all Views. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
WaitableEvent is a thread synchronization tool that allows one thread to wait for another thread to finish some work. This is equivalent to using a Lock+ConditionVariable to protect a simple boolean value. However, using WaitableEvent in conjunction with a Lock to wait for a more complex state change (e.g., for an item to be added to a queue) is not recommended. In that case consider using a ConditionVariable instead of a WaitableEvent. It is safe to create and/or signal a WaitableEvent from any thread. Blocking on a WaitableEvent by calling the *wait() functions is not allowed on the browser process UI or IO threads.
WebRTC handling policy types used by TChromiumCore.WebRTCIPHandlingPolicy.
Custom TWinControl used by CEF browsers.
A Window is a top-level Window/widget in the Views hierarchy. By default it will have a non-client area with title bar, icon and buttons that supports moving and resizing. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
Implement this structure to handle window events. The functions of this structure will be called on the browser process UI thread unless otherwise indicated.
Implement this interface to handle window events. The functions of this interface will be called on the browser process UI thread unless otherwise indicated.
Native Window handle.
Structure representing window information.
Wrapper class used to initialize a TCEFWindowInfo record.
The manner in which a link click should be opened. These constants match their equivalents in Chromium's window_open_disposition.h and should not be renumbered.
A Window is a top-level Window/widget in the Views hierarchy. By default it will have a non-client area with title bar, icon and buttons that supports moving and resizing. All size and position values are in density independent pixels (DIP) unless otherwise indicated. Methods must be called on the browser process UI thread unless otherwise indicated.
@@ -12527,107 +12552,107 @@ Ranges:
Structure the client can implement to provide a custom stream writer. The functions of this structure may be called on any thread.
Structure representing a X.509 certificate.
Structure representing the issuer or subject field of an X.509 certificate.
Supported XML encoding types. The parser supports ASCII, ISO-8859-1, and UTF16 (LE and BE) by default. All other types must be translated to UTF8 before being passed to the parser. If a BOM is detected and the correct decoder is available then that decoder will be used automatically.
XML node types.
Structure that supports the reading of XML data via the libxml streaming API. The functions of this structure should only be called on the thread that creates the object.
Structure that supports the reading of zip archives via the zlib unzip API. The functions of this structure should only be called on the thread that creates the object.
Class that supports the reading of zip archives via the zlib unzip API. The functions of this interface should only be called on the thread that creates the object.
Specifies the zoom commands supported by ICefBrowserHost.Zoom.
VCL and LCL version of TChromiumCore that puts together all browser procedures, functions, properties and events in one place. It has all you need to create, modify and destroy a web browser.
Parent class of TChromium and TFMXChromium that puts together all browser procedures, functions, properties and events in one place. It has all you need to create, modify and destroy a web browser.
The TChromiumFontOptions properties are used to fill the TCefBrowserSettings record which is used during the browser creation.
The TChromiumOptions properties used to fill the TCefBrowserSettings record which is used during the browser creation.
@@ -12638,237 +12663,237 @@ Ranges:
TChromiumWrapper
Cookie information.
This class handles all the ICefBrowserViewDelegate methods which call the ICefBrowserViewDelegateEvents methods. ICefBrowserViewDelegateEvents will be implemented by the control receiving the ICefBrowserViewDelegate events.
This class handles all the ICefButtonDelegate methods which call the ICefButtonDelegateEvents methods. ICefButtonDelegateEvents will be implemented by the control receiving the ICefButtonDelegate events.
This class handles all the ICefMenuButtonDelegate methods which call the ICefMenuButtonDelegateEvents methods. ICefMenuButtonDelegateEvents will be implemented by the control receiving the ICefMenuButtonDelegate events.
This class handles all the ICefPanelDelegate methods which call the ICefPanelDelegateEvents methods. ICefPanelDelegateEvents will be implemented by the control receiving the ICefPanelDelegate events.
Custom class implementing a resource filter with events.
Pascal version of TCefTaskInfo.
This class handles all the ICefTextfieldDelegate and ICefViewDelegate methods which call the ICefTextfieldDelegateEvents methods. ICefTextfieldDelegateEvents will be implemented by the control receiving the ICefTextfieldDelegate events.
This class handles all the ICefViewDelegate methods which call the ICefViewDelegateEvents methods. ICefViewDelegateEvents will be implemented by the control receiving the ICefViewDelegate events.
This class handles all the TCustomWindowDelegate methods which call the ICefWindowDelegateEvents methods. ICefWindowDelegateEvents will be implemented by the control receiving the TCustomWindowDelegate events.
TEmbeddedChromium @@ -12877,34 +12902,34 @@ Ranges:
2) TEmbeddedChromium adds InternalEvents that can be hooked by the component that owns the TEmbeddedChromium. This means the default published events are available to the end user. Published events that should not be available are hidden via THiddenPropertyEditor * Hidden event properties must not be assigned by any end user code. *
TEmbeddedOsrChromium
Hides (THiddenPropertyEditor) any published event that is used by TOsrBrowserWindow * Hidden events must also not be used by user code *
Record used by GetDLLVersion to get the DLL version information
TBufferPanel is used by FMX applications with browsers in OSR mode to draw the browser contents. See the FMXExternalPumpBrowser demo for more details.
FMX version of TChromiumCore that puts together all browser procedures, functions, properties and events in one place. It has all you need to create, modify and destroy a web browser.
@@ -12915,1197 +12940,1197 @@ Ranges:
String version of TCefLinuxWindowProperties
Record used with GetGlobalMemoryStatusEx to get the memory status.
ICefDisplayHandler
ICefRequestHandler
ICefContextMenuHandler
ICefLifeSpanHandler
ICefResourceRequestHandler
ICefPanelDelegate ICefBrowserViewDelegate
ICefButtonDelegate
ICefDownloadHandler
ICefCookieAccessFilter
ICefCommandHandler
ICefDevToolsMessageObserver
ICefDragHandler
ICefDialogHandler
ICefFindHandler
ICefFrameHandler
ICefRenderHandler
ICefAudioHandler
ICefResourceBundleHandler
ICefViewDelegate
ICefJsDialogHandler
ICefLoadHandler
ICefMenuButtonDelegate
ICefKeyboardHandler
ICefPrintHandler
ICefClient
ICefBrowserProcessHandler
ICefApp
ICefLoadHandler
ICefRequestContextHandler
ICefPermissionHandler
ICefRequestContextHandler uses the same TOnGetResourceRequestHandler event type defined for ICefRequestHandler ICefMediaObserver
ICefFocusHandler
ICefTextfieldDelegate
Custom
ICefRenderProcessHandler
ICefWindowDelegate
TOsrBrowserWindow - Off-Screen-Rendering @@ -14116,432 +14141,432 @@ Ranges:
This component is still experimental. - On MacOS Keyboard support is not complete
Record used with RtlGetVersion to get the Windows version information.
The TPDFPrintOptions properties are used to fill the TCefPdfPrintSettings record which is used in the TChromiumCore.PrintToPDF call.
Event type used by TChromiumCore.SimulateKeyEvent
User got to this page through a suggestion in the UI (for example, via the destinations page). Chrome style only.
Source is a subframe navigation. This is any content that is automatically loaded in a non-toplevel frame. For example, if a page consists of several frames containing ads, those ad URLs will have this transition type. The user may not even realize the content in these pages is a separate frame, so may not care about the URL.
This is a toplevel navigation. This is any content that is automatically loaded in a toplevel frame. For example, opening a tab to show the ASH screen saver, opening the devtools window, opening the NTP after the safe browsing warning, opening web-based dialog boxes are examples of AUTO_TOPLEVEL navigations. Chrome style only.
Attempted to visit a URL but was blocked.
The last transition in a redirect chain.
The beginning of a navigation chain.
Redirects caused by JavaScript or a meta refresh tag on the page.
Loaded a URL directly via CreateBrowser, LoadURL or LoadRequest.
Source is some other "explicit" navigation. This is the default value for navigations where the actual type is unknown. See also TT_DIRECT_LOAD_FLAG.
Source is a form submission by the user. NOTE: In some situations submitting a form does not result in this transition type. This can happen if the form uses a script to submit the contents.
Used the Forward or Back function to navigate among browsing history. Will be ORed to the transition type for the original load.
The transition originated from an external application; the exact definition of this is embedder dependent. Chrome style only.
User got to this page by typing in the URL bar and selecting an entry that did not look like a URL. For example, a match might have the URL of a Google search result page, but appear like "Search Google for ...". These are not quite the same as EXPLICIT navigations because the user didn't type or see the destination URL. Chrome style only. See also TT_KEYWORD.
User is navigating to the home page. Chrome style only.
Used to test whether a transition involves a redirect.
The url was generated from a replaceable keyword other than the default search provider. If the user types a keyword (which also applies to tab-to-search) in the omnibox this qualifier is applied to the transition type of the generated url. TemplateURLModel then may generate an additional visit with a transition type of TT_KEYWORD_GENERATED against the url 'http://' + keyword. For example, if you do a tab-to-search against wikipedia the generated url has a transition qualifer of TT_KEYWORD, and TemplateURLModel generates a visit for 'wikipedia.org' with a transition type of TT_KEYWORD_GENERATED. Chrome style only.
Corresponds to a visit generated for a keyword. See description of TT_KEYWORD for more details. Chrome style only.
Source is a link click or the JavaScript window.open function. This is also the default value for requests like sub-resource loads that are not navigations.
Source is a subframe navigation explicitly requested by the user that will generate new navigation entries in the back/forward list. These are probably more important than frames that were automatically loaded in the background because the user probably cares about the fact that this link was loaded.
General mask defining the bits used for the qualifiers.
Source is a "reload" of the page via the Reload function or by re-visiting the same URL. NOTE: This is distinct from the concept of whether a particular load uses "reload semantics" (i.e. bypasses cached data).
Redirects sent from the server by HTTP headers.
General mask defining the bits used for the source values.
String version of TCefUrlParts
Converts cef_time_t from time_t. time_t is almost always an integral value holding the number of seconds (not counting leap seconds) since 00:00, Jan 1 1970 UTC, corresponding to POSIX time.
If set user name, password, and cookies may be sent with the request, and cookies may be saved from the response.
If set the cache will not be used at all. Setting this value is equivalent to specifying the "Cache-Control: no-store" request header. Setting this value in combination with UR_FLAG_ONLY_FROM_CACHE will cause the request to fail.
Default behavior.
If set the ICefURLRequestClient.OnDownloadData method will not be called.
If set 5XX redirect errors will be propagated to the observer instead of automatically re-tried. This currently only applies for requests originated in the browser process.
If set the request will fail if it cannot be served from the cache (or some equivalent local store). Setting this value is equivalent to specifying the "Cache-Control: only-if-cached" request header. Setting this value in combination with UR_FLAG_SKIP_CACHE or UR_FLAG_DISABLE_CACHE will cause the request to fail.
If set upload progress events will be generated when a request has a body.
If set the cache will be skipped when handling the request. Setting this value is equivalent to specifying the "Cache-Control: no-cache" request header. Setting this value in combination with UR_FLAG_ONLY_FROM_CACHE will cause the request to fail.
If set 3XX responses will cause the fetch to halt immediately rather than continue through the redirect.
String type used by CEF. ustring was created to use the same type in Delphi and Lazarus.
Don't unescape anything at all.
Don't unescape anything special, but all normal unescaping will happen. This is a placeholder and can't be combined with other flags (since it's just the absence of them). All other unescape rules imply "normal" in addition to their special meaning. Things like escaped letters, digits, and most symbols will get unescaped with this mode.
Unescapes '/' and '\\'. If these characters were unescaped, the resulting URL won't be the same as the source one. Moreover, they are dangerous to unescape in strings that will be used as file paths or names. This value should only be used when slashes don't have special meaning, like data URLs.
URL queries use "+" for space. This flag controls that replacement.
Convert %20 to spaces. In some places where we're showing URLs, we may want this. In places where the URL may be copied and pasted out, then you wouldn't want this since it might not be interpreted in one piece by other applications.
Unescapes various characters that will change the meaning of URLs, including '%', '+', '&', '#'. Does not unescape path separators. If these characters were unescaped, the resulting URL won't be the same as the source one. This flag is used when generating final output like filenames for URLs where we won't be interpreting as a URL and want to do as much unescaping as possible.
Not configurable
Not enumerable
Writeable, Enumerable, Configurable
Not writeable
Lazarus and some old Delphi versions don't have these message contants
delay in ms to enable the browser focus <summary> YouTube restrict mode. </summary> <remarks> <para><see href="https://chromium.googlesource.com/chromium/src/+/refs/tags/77.0.3865.90/chrome/common/net/safe_search_util.h">Chromium source file: /chrome/common/net/safe_search_util.h (YouTubeRestrictMode)</see></para> <para><see href="https://www.chromium.org/administrators/policy-list-3#ForceYouTubeRestrict">Chromium policy list: https://www.chromium.org/administrators/policy-list-3#ForceYouTubeRestrict</see></para> </remarks>
function LoadCEFlibrary: boolean; virtual;function GetCookiesDir(const aRootDirectory : string) : string;function LoadCEFlibrary: boolean; virtual;function Load_cef_api_hash_h: boolean;function Load_cef_app_capi_h: boolean;function Load_cef_app_win_h: boolean;function Load_cef_browser_capi_h: boolean;function Load_cef_command_line_capi_h: boolean;function Load_cef_cookie_capi_h: boolean;function Load_cef_crash_util_h: boolean;function Load_cef_drag_data_capi_h: boolean;function Load_cef_dump_without_crashing_internal_h: boolean;function Load_cef_file_util_capi_h: boolean;function Load_cef_i18n_util_capi_h: boolean;function Load_cef_image_capi_h: boolean;function Load_cef_menu_model_capi_h: boolean;function Load_cef_media_router_capi_h: boolean;function Load_cef_origin_whitelist_capi_h: boolean;function Load_cef_parser_capi_h: boolean;function Load_cef_path_util_capi_h: boolean;function Load_cef_preference_capi_h: boolean;function Load_cef_print_settings_capi_h: boolean;function Load_cef_process_message_capi_h: boolean;function Load_cef_process_util_capi_h: boolean;function Load_cef_request_capi_h: boolean;function Load_cef_request_context_capi_h: boolean;function Load_cef_resource_bundle_capi_h: boolean;function Load_cef_response_capi_h: boolean;function Load_cef_scheme_capi_h: boolean;function Load_cef_server_capi_h: boolean;function Load_cef_shared_process_message_builder_capi_h: boolean;function Load_cef_ssl_info_capi_h: boolean;function Load_cef_stream_capi_h: boolean;function Load_cef_task_capi_h: boolean;function Load_cef_task_manager_capi_h: boolean;function Load_cef_thread_capi_h: boolean;function Load_cef_trace_capi_h: boolean;function Load_cef_urlrequest_capi_h: boolean;function Load_cef_v8_capi_h: boolean;function Load_cef_values_capi_h: boolean;function Load_cef_waitable_event_capi_h: boolean;function Load_cef_xml_reader_capi_h: boolean;function Load_cef_zip_reader_capi_h: boolean;function Load_cef_logging_internal_h: boolean;function Load_cef_string_list_h: boolean;function Load_cef_string_map_h: boolean;function Load_cef_string_multimap_h: boolean;function Load_cef_string_types_h: boolean;function Load_cef_thread_internal_h: boolean;function Load_cef_trace_event_internal_h: boolean;function Load_cef_browser_view_capi_h: boolean;function Load_cef_display_capi_h: boolean;function Load_cef_label_button_capi_h: boolean;function Load_cef_menu_button_capi_h: boolean;function Load_cef_panel_capi_h: boolean;function Load_cef_scroll_view_capi_h: boolean;function Load_cef_textfield_capi_h: boolean;function Load_cef_window_capi_h: boolean;function Load_cef_types_linux_h: boolean;function Load_cef_time_h: boolean;procedure doOnBeforeCommandLineProcessing(const processType: ustring; const commandLine: ICefCommandLine); virtual;procedure doOnRegisterCustomSchemes(const registrar: TCefSchemeRegistrarRef); virtual;procedure doOnRegisterCustomPreferences(type_: TCefPreferencesType; registrar: PCefPreferenceRegistrar); virtual;procedure doOnContextInitialized; virtual;procedure doOnBeforeChildProcessLaunch(const commandLine: ICefCommandLine); virtual;procedure doOnAlreadyRunningAppRelaunch(const commandLine: ICefCommandLine; const current_directory: ustring; var aResult: boolean); virtual;procedure doOnScheduleMessagePumpWork(const delayMs: Int64); virtual;procedure doGetDefaultClient(var aClient : ICefClient); virtual;procedure doGetDefaultRequestContextHandler(var aRequestContextHandler : ICefRequestContextHandler); virtual;function doGetLocalizedString(stringid: Integer; var stringVal: ustring): Boolean; virtual;function doGetDataResource(resourceId: Integer; var data: Pointer; var dataSize: NativeUInt): Boolean; virtual;function doGetDataResourceForScale(resourceId: Integer; scaleFactor: TCefScaleFactor; var data: Pointer; var dataSize: NativeUInt): Boolean; virtual;procedure doOnWebKitInitialized; virtual;procedure doOnBrowserCreated(const browser: ICefBrowser; const extra_info: ICefDictionaryValue); virtual;procedure doOnBrowserDestroyed(const browser: ICefBrowser); virtual;procedure doOnContextCreated(const browser: ICefBrowser; const frame: ICefFrame; const context: ICefv8Context); virtual;procedure doOnContextReleased(const browser: ICefBrowser; const frame: ICefFrame; const context: ICefv8Context); virtual;procedure doOnUncaughtException(const browser: ICefBrowser; const frame: ICefFrame; const context: ICefv8Context; const V8Exception: ICefV8Exception; const stackTrace: ICefV8StackTrace); virtual;procedure doOnFocusedNodeChanged(const browser: ICefBrowser; const frame: ICefFrame; const node: ICefDomNode); virtual;procedure doOnProcessMessageReceived(const browser: ICefBrowser; const frame: ICefFrame; sourceProcess: TCefProcessId; const aMessage: ICefProcessMessage; var aHandled : boolean); virtual;procedure doOnLoadingStateChange(const browser: ICefBrowser; isLoading, canGoBack, canGoForward: Boolean); virtual;procedure doOnLoadStart(const browser: ICefBrowser; const frame: ICefFrame; transitionType: TCefTransitionType); virtual;procedure doOnLoadEnd(const browser: ICefBrowser; const frame: ICefFrame; httpStatusCode: Integer); virtual;procedure doOnLoadError(const browser: ICefBrowser; const frame: ICefFrame; errorCode: TCefErrorCode; const errorText, failedUrl: ustring); virtual;procedure ShutDown;procedure FreeLibcefLibrary;function ExecuteProcess(const aApp : ICefApp) : integer;procedure InitializeCefMainArgs(var aCefMainArgs : TCefMainArgs);procedure InitializeSettings(var aSettings : TCefSettings);function InitializeLibrary(const aApp : ICefApp) : boolean;procedure RenameAndDeleteDir(const aDirectory : string; aKeepCookies : boolean = False);procedure DeleteCacheContents(const aDirectory : string);procedure DeleteCookiesDB(const aDirectory : string);procedure DeleteCookiesDB(const aRootDirectory : string);procedure MoveCookiesDB(const aSrcDirectory, aDstDirectory : string);function MultiExeProcessing: boolean;function SingleExeProcessing: boolean;procedure BeforeInitSubProcess; virtual;function CheckCEFResources: boolean; virtual;function CheckCEFDLL: boolean; virtual;function CheckWindowsVersion: boolean; virtual;function CheckOSVersion: boolean; virtual;procedure ShowErrorMessageDlg(const aError : string); virtual;function ParseProcessType: TCefProcessType;procedure AddCustomCommandLineSwitches(var aKeys, aValues : TStringList); virtual;procedure AppendSwitch(var aKeys, aValues : TStringList; const aNewKey : ustring; const aNewValue : ustring = '');procedure ReplaceSwitch(var aKeys, aValues : TStringList; const aNewKey : ustring; const aNewValue : ustring = '');procedure CleanupFeatures(var aKeys, aValues : TStringList; const aEnableKey, aDisableKey : string);procedure ClearSchemeHandlerFactories;
constructor Create;destructor Destroy; override;procedure AfterConstruction; override;procedure AddCustomCommandLine(const aCommandLine : string; const aValue : string = '');function CheckCEFLibrary: boolean;function StartMainProcess: boolean;function StartSubProcess: boolean;procedure DoMessageLoopWork;procedure RunMessageLoop;procedure QuitMessageLoop;procedure UpdateDeviceScaleFactor; virtual;function ValidComponentID(aComponentID : integer) : boolean;function NextComponentID: integer;procedure RemoveComponentID(aComponentID : integer);function DumpWithoutCrashing(mseconds_between_dumps: int64; const function_name, file_name: ustring; line_number: integer): boolean;function DumpWithoutCrashingUnthrottled: boolean; |
+function GetCookiesDir(const aRootDirectory : string) : string; |
+
|
+ This item has no description. | |
|
function LoadCEFlibrary: boolean; virtual; |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
@@ -4010,7 +4022,7 @@ ICefLoadHandler
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
