The
WebBrowser
control is just a thin wrapper around an ActiveX control. As such, it suffers from airspace problems in WPF applications, and there's no easy way to resolve that.
Mitigating Airspace Issues In WPF Applications - Presentation Source - Site Home - MSDN Blogs[
^]
(This was going to be fixed in .NET 4.5, but they ended up dropping it before release.)
Also, unless you tweak the registry on every computer that runs your application, the control is
stuck in IE7 mode[
^]. That means you can't use any modern features in the pages you display, and some sites might not work at all.
The solution is to use a proper WPF control which doesn't have these problems. Your best bet is probably
CEFSharp[
^], which uses the same rendering engine as Google Chrome. There's even a
WPF Quick Start guide[
^] here on CodeProject.