WebBrowser control not visible

[ssolomon]

In the version available via Nuget, WebBrowser controls on a page are visible. However, on the current latest, WebBrowsers controls are not displaying their content. The content is there, and you are able to view source, but the contents are not visible. This could be related to a known issue with WebBrowser controls when used in a windows with AllowsTransparancy turned on.

[punker76]

The WebBrowser wrap around native controls. Since they use a different graphics engine than WPF, you may be running into the Airspace issue as shown here: #488

[ssolomon]

Thanks your response. As the mentioned previously and as the other issue also refers, I am sure the issue is related to Window Transparency. I know the Linked issue talks about a work around, but this is far from ideal. This issue has been introduced with the last source code, but was not an issue in the current release, so suggesting using a workaround does not really feel like a solution.

[punker76]

@ssolomon another solution is to remove the transparency by hand. put this lines in your MetroWindow xaml and all should work (same as in MetroDemo.InteropDemo):

  xmlns:i="clr-namespace:System.Windows.Interactivity;assembly=System.Windows.Interactivity"

<i:Interaction.Behaviors>
    <behaviours:BorderlessWindowBehavior ResizeWithGrip="True" AllowsTransparency="False" />
</i:Interaction.Behaviors>

[punker76]

@ssolomon is this issue still present?

[michaelmairegger]

I had the same issue with a ReportViewer in connectin with WindowsFormHost. Your solution with the behaviours works. Thanks a lot.

[ssolomon]

I have not tried the solution with the behaviour yet. But still does not feel right that I need to use a behaviour to fix this.

[punker76]

@ssolomon he, i give you two solutions to fix a windows wpf problem. what next?

[AzureKitsune]

@ssolomon We can't "fix" the issue of the differences in the graphics engine between WPF and Windows Forms. Turning off Transparency or using the Airspace decorator are both solutions to this issue. It is a known WPF issue, not a MahApps.Metro one.

If you really don't want to use a behavior, set AllowsTransparency (directly on your window) to false.

[ssolomon]

Hi. Thanks for you comment. I am aware that it is an issue in WPF and not something you can 'fix'. The point I was making was that in older versions of the library, everything was fine, so you obviously introduced something later that made the issue occur. The other point I was making was that setting AllowsTransparancy directly on the window did NOT work. However, using the behaviour does, and I am happy to go with approach. Cheers.

[djmiller9975]

I'm trying your solution above and VS tells me that AllowsTransparency is not recognized or inaccessible. It doesn't let me pick anything after BorderlessWindowBehavior