Hi,

You do not have to worry about whether the WebView is ready to load a page. You can set its Url property BEFORE it is ready to load. In that case as soon as it is fully initialized it will start to load the page.

When you see a complete blank page, there are several possibilities:

1. The WebControl has not been initialized properly at all;
2. It is initialized but it is not sized or positioned properly (for example, it could have a size of 0 by 0, or it is positioned outside of the visible area of the parent window);
3. The page you loaded indeed is a blank page;

For issue #1 and #2, you can use Visual Studio's built-in Spy++ tool to check both. When you see a blank page, open Spy++, then use the window finder tool to locate the tab window. This is the parent window of the WebControl.

From there on you should see a number of child windows in Spy++. The window tree should look something like this:



The exact numbers can be different but the window tree structure should be similar. The first line is the parent control of the WebControl (possibly a tab in your case). The second line is the WebControl. The third line and on are the internal windows created by the browser engine. You want to check:

1. You have a similar window tree. If not, then the WebControl is not properly intialized;
2. Right click each window and check their properties to make sure their position and size are correct;

If #2 is the problem, then you will need to debug your code to make sure that the WebControl is properly sized and positioned.

To troubleshoot #3, you can use the WebBrowser's built-in debug feature to check the page contents:

https://www.essentialobjects.com/doc/webbrowser/advanced/debug.aspx

If the page's content is indeed empty, then you will need to debug on your end to find out why. Obviously we have no way of telling why your server responded with an empty page.

If none of the those is the issue or if you see the WebControl not initialized at all (case #1), then you can try to isolate the problem into a test project and send the test project to us:

https://www.essentialobjects.com/forum/test_project.aspx

Once we have that we will be happy to investigate further.

Hope this helps.

Thanks!

Hi,

The "Intermediate D3D Window" is the GPU's "composition surface" that produces the final output, so it does need to be the last one (to be on top). There might be some specific window styles you are setting in your application or the tabs that have impacted this. If GPU accelaration is not important for you, you can try to turn it off:



Once the GPU is turned off, this window will not be created.

If that still does not resolve the issue, you can try to isolate the problem into a test project and send the test project to us:

https://www.essentialobjects.com/forum/test_project.aspx

We will be happy to investigate further once we have that.

Thanks!

Glad to hear that. You can PM us your order number and the exact version you need and we will provide the download link to you.