All Constants

* ****************************************************** ****************** OTHER CONSTANTS ******************* ****************************************************** *

Platform API hash.

Universal API hash. (deprecated, same as CEF_API_HASH_PLATFORM)

value defined in /include/cef_api_hash.h

values defined in cef_api_versions.json

Cookie priority values.

Chrome toolbar types.

The browser crashed. Internal use only: resume pending downloads if possible.

The file was blocked due to local policy.

The partial file didn't match the expected hash.

There is not enough room on the drive.

An attempt to check the safety of the download failed due to unexpected reasons. See http://crbug.com/153212.

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 contains a virus.

Generic network failure.

The server has gone down.

No interrupt reason.

Server certificate problem.

An unexpected cross-origin redirect happened.

Server access forbidden.

Server didn't authorize access to resource.

The user canceled the download.

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 video capture permission.

Device video capture permission.

Modifier values used in the Input.dispatchTouchEvent and Input.dispatchMouseEvent DevTools methods. Bit field representing pressed modifier keys. Alt=1, Ctrl=2, Meta/Command=4, Shift=8 (default: 0). https://chromedevtools.github.io/devtools-protocol/tot/Input/#method-dispatchTouchEvent

Result codes for ICefMediaRouter.CreateRoute. Should be kept in sync with Chromium's media_router::mojom::RouteRequestResultCode type.

This value may be used with the mseconds_between_dumps parameter in GlobalCEFApp.DumpWithoutCrashing.

Used when the shared textures are disabled.

Direct proxy type: Never use a proxy.

Pac_script proxy type: Use a .pac proxy script.

The process is of an unknown type.

Last Chrome result code.

Chrome was downgraded since the last launch. Perform downgrade processing and relaunch.

The GPU process exited because initialization failed.

Process hung.

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.

A browser process was sandboxed. This should never happen.

A bad message caused the process termination.

A critical chrome file is missing.

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.

The browser process exited early by passing the command line to another running browser.

A dummy value we should not use. See crbug.com/152285.

Last TCefResultCode value.

The profile was in use on another host.

Windows sandbox broker terminated in shutdown.

Windows sandbox failed to close pending handles.

First Sandbox result code.

Windows sandbox could not set the integrity level.

Windows sandbox exceeded the job memory limit.

Windows sandbox failed to warmup.

Failed to migrate user data directory for side-by-side package support (Linux-only).

Uninstall detected another chrome instance.

Failed to silently uninstall an extension.

Command line parameter is not supported.

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_FETCH_ENABLED is set the scheme can perform Fetch API requests.

No options.

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

In particular, the syntax for standard scheme URLs must be of the form: <pre> [scheme]://[username]:[password]@[host]:[port]/[url-path] </pre> Standard scheme URLs must have a host component that is a fully qualified domain name as defined in Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123. These URLs will be canonicalized to "scheme://host/path" in the simplest case and "scheme://username:password@host:port/path" in the most explicit case. For example, "scheme:host/path" and "scheme:///host/path" will both be canonicalized to "scheme://host/path". The origin of a standard scheme URL is the combination of scheme, host and port (i.e., "scheme://host:port" in the most explicit case).

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 maximized.

Show the window as normal.

Values indicating what state of the touch handle is set.

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.

A subframe page is selected.

A media node is selected.

The top page 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

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.

Print job duplex mode values.

Permission to access a resource, other than the network, was denied.

Returned when attempting to bind an address that is already in use.

An error adding a certificate to the OS certificate database.

The SSL handshake failed because of a bad or missing client certificate.

The client chose to block the request.

The request was blocked by fingerprinting protections.

The connection is blocked by private network access checks.

The IP address space of the cached remote endpoint is blocked by private network access check.

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 disk cache is unable to create 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.)

The cache does not have the requested entry.

The disk cache is unable to open or create 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 write to the disk cache.

The server responded with a certificate that is signed by an authority we don't trust. The could mean:

1. An attacker has substituted the real certificate for a cert that contains their public key and is signed by their cousin.

2. The server operator has a legitimate certificate from a CA we don't know about, but should trust.

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 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 server responded with a certificate that, by our clock, appears to either not yet be valid or to have expired. This could mean:

1. An attacker is presenting an old certificate for which they have managed to obtain the private key.

2. The server is misconfigured and is not presenting a valid cert.

3. Our clock is wrong.

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 claimed DNS names that are in violation of name constraints.

The certificate has no mechanism for determining if it is revoked. In effect, this certificate cannot be revoked.

The certificate chained to a legacy Symantec root that is no longer trusted. https://g.co/chrome/symantecpkicerts

The certificate's validity period is too long.

The server responded with a certificate that contains a weak key (e.g. a too-small RSA key).

The request was blocked by system policy disallowing some or all cleartext requests. Used for NetworkSecurityPolicy on Android.

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 attempt failed.

A connection was reset (corresponding to a TCP RST).

Content decoding of the response body failed.

The HTTP response body transferred fewer bytes than were advertised by the Content-Length header when the connection is closed.

Certificate Transparency: Failed to parse the received consistency proof.

Certificate Transparency: Received a signed tree head that failed to parse.

The scheme of the URL is disallowed.

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.

All DNS requests associated with this job have been cancelled.

When checking whether secure DNS can be used, the response returned for the requested probe record either had no answer or was invalid.

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.

Failed to sort addresses according to RFC3484.

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, but the server was unable to decrypt the encrypted ClientHello.

Converting the response to target encoding failed.

A generic failure occurred.

The file or directory cannot be found.

The path or file name is too long.

The file has a virus.

There are too many pending DNS resolves, so a request in the queue was aborted.

HTTP_1_1_REQUIRED error code received on HTTP/2 session.

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 - not a CA cert.

Server certificate import failed due to some internal error.

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 server's response was insecure (e.g. there was a cert error).

The Internet connection has been lost.

Credentials could not be established during HTTP Authentication.

The ECHConfigList fetched over DNS cannot be parsed.

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.

The server's response was invalid.

The URL is invalid.

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.

The identity used for authentication is invalid.

The server did not support the request method.

(GSSAPI) No Kerberos credentials were available during HTTP Authentication.

The host name could not be resolved.

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 network changed.

No error.

No socket buffer space is available.

No SSL protocol versions are enabled.

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.

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 PAC script terminated fatally and must be reloaded.

PKCS #12 import failed due to other error.

PKCS #12 import failed due to invalid MAC.

We've hit the max socket limit for the socket pool while preconnecting. We don't bother trying to preconnect more sockets.

The proxy requested authentication (for tunnel establishment).

The proxy requested authentication (for tunnel establishment) with an unsupported method.

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.

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.

The QUIC crypto handshake failed. This means that the server was unable to read any requests sent, so they may be resent.

Socket ReadIfReady support is not implemented. This error should not be user visible, because the normal Read() method is used as a fallback.

The HTTP response was too big to drain.

The HTTP response contained multiple distinct Content-Length headers.

The headers section of the response is too large.

Self-signed certificate generation failed.

The socket is not connected.

Failed to set the socket's send buffer size as requested, despite success return code from setsockopt.

Failed to set the socket's send buffer size as requested.

The SOCKS proxy server failed establishing connection to the target host because that host is unreachable.

The peer violated HTTP/2 flow control.

Transport security is inadequate for the HTTP/2 version.

There is an HTTP/2 protocol error.

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.

SSL peer's public key is invalid.

Failed to import a client certificate from the platform store into the SSL library.

The SSL client certificate has no private key.

The permission to use the SSL client certificate's private key was denied.

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 operation failed because the SSL handshake has not completed.

The peer sent an SSL no_renegotiation alert message.

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.

The server requested a renegotiation (rehandshake).

The SSL server certificate changed in a renegotiation.

The client and server don't support a common SSL protocol version or cipher suite.

The request throttler module cancelled this request to avoid DDOS.

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.)

Attempting to load an URL resulted in too many redirects.

A Trust Tokens protocol operation-executing request failed for one of a number of reasons (precondition failure, internal error, bad response).

A tunnel connection through the proxy could not be established.

An undocumented SSPI or GSSAPI status code was returned.

The header of dictionary compressed stream does not match the expected value.

An unexpected, but documented, SSPI or GSSAPI status code was returned.

The server sent an FTP directory listing in a format we do not understand.

Attempting to load an URL resulted in an unsafe redirect (e.g., a redirect to file:// is considered unsafe).

The file upload failed because the file's modification time was different from the expectation.

Winsock sometimes reports more data written than passed. This is probably due to a broken LSP.

Websocket protocol error. Indicates that we are terminating the connection due to a malformed frame or other protocol violation.

When a WebSocket handshake is done successfully and the connection has been upgraded, the URLRequest is cancelled with this error code.

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 allows picking multiple files to open.

Default behavior.

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.

for InitLibLocationFromArgs

Default logging (currently INFO logging).

ERROR logging.

INFO logging.

WARNING logging.

Prepend the process ID.

Prepend the tickcount.

Prepend no items.

Navigation.

Custom menu items originating from the renderer process.

Miscellaneous.

Spell checking word correction suggestions.

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.

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.

The last transition in a redirect chain.

Redirects caused by JavaScript or a meta refresh tag on the page.

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.