Hi,

EO.WebBrowser does not support Adorner Layer or Busy Indicators yet. Internally it uses a window handle which prevents you from overlaying other WPF control on it. To use BusyIndicator, you must use it in a separate window. We will continue to research to see how we can support them seamlessly.

The little UI lock is due to the time EO.WebBrowser spends to initialize its internal browser engine. You can try to use our multi-DLL build to decrease the intiaization time:

http://www.essentialobjects.com/doc/6/install/multi_dll_build.aspx

If that still does not help and you do not need to display the WebView immediately after your application starts, you can use the ThreadRunner class to create an invisible WebView in a background thread to initialize the browser engine:



This will initialize the browser engine so that later WebView creation will be faster. Note that you must also call webView.Destroy() to destroy this WebView when your application exits.

Hope this helps. Please feel free to let us know if you have any more questions.

Thanks!

You are welcome. Yes, you are correct. You can use a dialog. But you can not use another control overlay on top of the browser inside the same window. Airspace issue is exactly the root of the problem.

Thanks!