November 12, 2013, Chromium 29.0 / CEF 3.1547.1412
- Second public beta version of CEF3-based port. [@plundberg]
- Upgraded to CEF 3.1547.1412, which provides Chromium 29 support as well as support for x64. [@plundberg]
- Breaking change: Changed ISchemeHandler to use asynchronous processing of requests (to avoid having to perform network traffic/heavy processing on the UI thread) instead of synchronous processing. [@plundberg]
- Added the possibility for a custom scheme handler to override the response HTTP headers. [@plundberg]
- #80: Fixed the "process not closing in Windows XP" bug. [@rastating]
- #137: NuGet packages for WPF, using .props and .targets MSBuild tricks to make consumption of the package a lot less painful. [@plundberg]
- #138: Added a separate browser subprocess .exe file, which is normally a much more preferable approach than just executing your .NET application's .exe file again. (which is the default with CEF) [@plundberg]
- #150: All schemes were registered as non-standard, as pointed out by @alexwarren. This has now been fixed; the API for registering custom schemes also had to go through a bit of a breakage in the meanwhile since the way this works with CEF made it impossible to use the previous semantics. [@plundberg]
- #157: Made it possible to customize BrowserSettings directly in XAML. [@plundberg, as suggested by Clemens Hoffmann]
- #160: Added support for x64. [@plundberg]
- #161: Make the WPF WebView be transparent (using the alpha channel), so that you can allow HTML content to be rendered on top of WPF content, allowing for some nifty, more complex scenarios. [@dcartwright]
- #184: Additional SchemeHandlerResponse options. [@provegard]
- #209: Support for
ExecuteScriptAsync()andEvaluateScript()in the WPF WebView, making it possible to support more trivial JS integration scenarios. [@plundberg] - #210: Added support for Windows Forms again. [@uowzd01]