Setting the Timeout property specifies the number of seconds
to wait for the navigation to complete.
If the timeout period is set to zero, the control does not enforce its
own timer and instead relies on the default timeouts implemented by the
WebView2 engine. These built-in timeouts automatically handle conditions
such as slow DNS resolution, stalled connections, or unreachable servers,
and generally behave in the same way as the Microsoft Edge browser.
If a non-zero timeout period is specified, the control will cancel
the navigation if the internal timer exceeds that value and the page
has not finished loading. When this occurs, the navigation is stopped
and a timeout error is reported through the standard navigation event
notifications. This allows applications to fail fast in cases where a
site is not responding, rather than waiting for the browser's adaptive
timeouts to expire.
Note that specifying a very large timeout value will not
force the browser to wait indefinitely. The WebView2 engine may still
apply its own internal maximums and terminate the navigation earlier
if it decides the request cannot succeed. Applications should select
timeout values that balance responsiveness and reliability.