Limitations of using WebBrowser control to create WPF apps

Question

I've recently stumbled across WebBrowser WPF control. I am interested if there are any limitations when building user interfaces with HTML+CSS+JS and embedding them in WebBrowser.

So far I've successfully

• intercepted HTML click events and handled them in C# using [ComVisible(true)] class attribute

• called JS script from C# using InvokeScript method.

  InvokeScript also supports sending objects to the HTML/JS via parameters which faciliates two way communication.

Is there any reason for not using using WebBrowser to create simple apps? I am intersted in parts that absolutely need to be handled with some WPF code and cannot be bridged using WebBrowser.