Hi,
This is normal. The delay occurs when the browser engine initializes, which only happens if:
1. When a WebView's parent window has been created. This is what caused the difference in your case;
2. If you use HTML to PDF converter, when your use HTML to PDF to start the first conversion;
When you use a PDFViewer, it actually falls to the first case because internall PDFViewer uses WebView. Note that the browser engine used by case #1 and case #2 are different, which means starting the browser engine for case #2 won't solve problems for #1.
One way you can optimize this problem is to initialize the browser engine early. For example, you can call this code as soon as your application starts:
Code: C#
WebView.Preload("about:blank");
Or you can use a new ThreadRunner to create a empty WebView completely in the background thread:
https://www.essentialobjects.com/doc/webbrowser/start/webview_no_ui.aspxBoth methods will intialize the browser engine thus by the time you really need the WebView in your UI, the engine is already initialized thus you won't notice much delay.
Obviously this only works if you do not need the browser engine/WebView right away.
Thanks!