5 ms·
The WPF browser control is pretty weak. You don't have great control over which rendering engine it will use (default is to go to IE 7 mode!) except via writing
by myoon 11y ago
The WPF browser control is pretty weak. You don't have great control over which rendering engine it will use (default is to go to IE 7 mode!) except via writing a registry key to switch it. It provides almost no bridge between the JS and native code as well. I haven't used CefSharp, but I have used Awesomium, which provided pretty good JS-C# bindings, so I assume CefSharp has at least working JS-C# bindings.
- m_fayer 11y agoI've also had a great experience with awesomium which imo has a more powerful api than cefsharp, I'm curious why they chose it over awesomium.
- julionc 11y agoI guess the reason is that they (Awesomium) don't provide an Open Source license like MIT or GPL. Instead Github Team choose CefSharp.