3.29.0-pre.0

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() and EvaluateScript() in the WPF WebView, making it possible to support more trivial JS integration scenarios. [@plundberg]
• #210: Added support for Windows Forms again. [@uowzd01]

1.25.5

October 2 2013, Chromium 25.0.1364.1123

#162: Fixed support for HTML drop-downs which probably has been broken since 1.25.1. [@ChadyG] #165: Add bindings for SetZoomLevel in WPF. [@peters with @plundberg] #166: Fixed blurriness in CefSharp.Wpf when running in DPI settings different than 100% (i.e. when the user has modified the "font size" in the Windows display settings). [@plundberg]

1.25.4

September 4, 2013, Chromium 25.0.1364.1123

• #150: All schemes are registered as non-standard. Not truly fixed, but let's at least remove the is_standard flag for a while to decrease the confusion. [@plundberg with @alexwarren]
• #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]
• 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]

1.25.3

August 14, 2013, Chromium 25.0.1364.1123

• Added signing to CefSharp.WinForms and CefSharp.Wpf [@dabide]
• Add support for parameters of type 'Object' accepting any type of value. [@EMonk72]
• Fix object binding to allow multiple methods with same name. [@EMonk72]
• Reimplemented Javascript-to-.NET binding to support a range of options including C#-style param arrays and optional parameters
  with default values. [@EMonk72]
• Added support for accessing the body of the request in a custom scheme handler. [@kpko]
• Added support for overriding the window.alert(), window.confirm() and window.prompt() methods by using the new IJsDialogHandler
  interface + the new IWebBrowser.JsDialogHandler property, which is presumed to be your own implementation of this interface.
  [@KristinaKoeva]
• Fixed a null pointer exception that occurs when WebView is loaded. [@joaompneves]
• Fixed crash on window deactivate. [@joaompneves]

3.27.0-a0

First alpha version of CefSharp 3.

• Only WPF
• No JS bindings
• Quite possibly a number of other issues.

Still, it's an "early bird" preview for those who wish to take a look at it.