The only supported alpha values are 0 and 255, all other values will result in exception. Semi-transparent colors are not currently supported by this API and setting DefaultBackgroundColor to a semi-transparent color will fail with an exception. It is supported on all other WebView compatible platforms.
#Xojo properties windows#
Any A value other than 255 will result in an exception on Windows 7. This Alpha value is not supported on Windows 7. In the case of a transparent DefaultBackgroundColor WebView will render hosting app content as the background. The A represents an Alpha value, meaning DefaultBackgroundColor can be transparent. The Color is specified by the color that represents an RGBA value. The default value for this property is white to resemble the native browser experience. Web pages with defined and opaque background properties that span the page will obscure the DefaultBackgroundColor and display normally. This also means web pages with undefined css background properties or background properties containing transparent pixels will render their contents over this color. This means WebView renders this color when there is no web content loaded such as before the initial navigation or between navigations. The DefaultBackgroundColor property is the color WebView renders underneath all web content. When such a path is used, the API fails with HRESULT_FROM_WIN32(ERROR_NOT_SUPPORTED). The path of fixed version of the WebView2 Runtime should not contain \Edge\Application\. In this scenario, the API tries to find a compatible version of the WebView2 Runtime that is installed on the user machine (first at the machine level, and then per user) using the selected channel preference.
To create WebView2 controls that use the installed version of the WebView2 Runtime that exists on user machines, pass a empty string to browserExecutableFolder. To use a fixed version of the WebView2 Runtime, pass the relative folder path that contains the fixed version of the WebView2 Runtime to browserExecutableFolder. Use browserExecutableFolder to specify whether WebView2 controls use a fixed or installed version of the WebView2 Runtime that exists on a user machine. in Configure event, before initialization of the control runs. The path to the browser executable to use. Needs WebView2 in version 1.0.864.35 or newer. The default value for AreBrowserAcceleratorKeysEnabled is true. The event will be fired for all accelerator keys, whether they are enabled or not. This setting has no effect on the AcceleratorKeyPressed event. Those accelerator keys will always be enabled unless they are handled in the AcceleratorKeyPressed event. It does not disable accelerator keys related to movement and text editing, such as: Special keys for browser functions, such as Back, Forward, and Search When this setting is set to false, it disables all accelerator keys that access features specific to a web browser, including but not limited to:
Whether all accelerator keys are enabled. areBrowserAcceleratorKeysEnabled as Boolean Default is to run browser process with no extra flags.
If parsing failed for the specified switches, they will be ignored. Certain features are disabled internally and can't be enabled. App process's command line -edge-webview-switches value are processed after the additionalBrowserArguments parameter is processed. The features specified by -enable-features and -disable-features will be merged with simple logic: the features will be the union of the specified features and built-in features, and if a feature is disabled, it will be removed from the enabled features list. There is no attempt to merge the different values of the same switch, except for disabled and enabled features. If the same switches are specified multiple times, the last one wins. Those switches will be ignored even if specified. Certain switches like -user-data-dir are internal and important to WebView. If the app is launched with a command line switch -edge-webview-switches=xxx the value of that switch (xxx in the above example) will also be appended to the browser process command line. See Run Chromium with Flags for more information about command line switches to browser process. These will be passed to the browser process as part of the command line. AdditionalBrowserArguments as StringĪdditional browser arguments can be specified to change the behavior of the WebView.
0 kommentar(er)
