Reputation: 7642
What are the limitations of WPF web browser control? Is it good enough for a real-life browser implementation? And is it a fully managed implementation?
Upvotes: 2
Views: 1442
Reputation: 4213
Adding to the answers by @Kyle and @Reed, below are my observations as limitations.
Upvotes: 0
Reputation: 25277
It is good enough for Real-life use, and I agree with Reeds view on the matter.
Additionaly, If a person does not have certain IE files on their computer the control is rendered useless. Here are a few observed limitations I have found:
WebBrowser
controls is it's hatred of IE6 on a computer whilst trying to perform JavaScript insertions within the control. (Very machine-specific though, so you could say lack of total compatibility?)HtmlElement
.All in all, the control could be greatly improved, and to honest it would be fantastic to see the .NET team make a fully managed version of this component.
Cheers,
Kyle
Upvotes: 1
Reputation: 564373
The WPF WebBrowser control is just an interop layer hosting the IE ActiveX control. It should be very robust, and usable for a real-life browser (since it's really IE). It is not a managed implementation.
Its main limitations are due to the fact that it's using an HwndHost internally. This means that it has the WPF/Native airspace issues, as well as some minor issues with event handling.
Upvotes: 2