New Release: Awesomium 1.6.3!

We are pleased to announce the release of Awesomium v1.6.3! This release is chock-full of new features, fixes, and a super-sweet Windows installer— view the top changes below.

Top 5 Core Changes

1. History Database API

We’ve added a bit of API to the WebCore class so that you can query the on-disk history database (see WebCore::queryHistory). This is useful for displaying a list of recently-visited pages or for creating auto-complete address boxes. Please note that this method requires that you enable SaveCacheAndCookies in the config.

2. Context Menus

Whenever a user clicks the right mouse-button, the page will fire a request to show the context menu (see WebViewListener::onShowContextMenu). It is the embedder’s responsibility to handle the event, display the menu, and handle any action the user selects.

3. Authentication Dialogs

We’ve added support for authentication dialogs for Basic HTTP Auth, NTLM Auth, and Proxy Auth (see WebViewListener::onRequestLogin). It is the embedder’s responsibility to handle the event, display the dialog, and then, once the user has chosen an action, call WebView.login or WebView.cancelLogin.

4. Javascript Dialogs

We’ve also added support for Javascript Dialogs (eg, alert, confirm, and prompt). It is the embedder’s responsibility to handle the event, display the proper dialog, and then, once the user has chosen an action, call WebView.closeJavascriptDialog.

5. Improved Handling of Config Paths

Rewrote the way we handle config paths, now embedders can specify a “packagePath” that will be used to resolve all relative config paths. Embedders can now also specify a “localePath” for the location of en-US.dll on Windows and chrome.pak on Linux.

Top 8 .NET Changes

  1. AwesomiumSharp has been renamed Awesomium.NET and will be closed-source from this point forward.
  2. The dependency model has been redesigned, Awesomium.NET is now comprised of four assemblies:
    • Awesomium.Core (WebCore, WebView, etc.)
    • Awesomium.Windows.Controls (WPF specific)
    • Awesomium.Windows.Forms (WinForms specific)
    • Awesomium.Mono (Mono specific)
  3. Rendering performance has been noticeably improved
  4. Visual Studio integration has been greatly improved. The Windows installer now includes project templates and will automatically register all .NET controls in your VS Toolbox. (Please note the WinForms control is still experimental.)
  5. On Windows, Awesomium will be installed into the GAC (Global Assembly Cache) and all dependencies will be automatically deployed to your output directory when you link against the managed assembly.
  6. Child Process configuration has been added. This will allow you to use your own executable to host the WebView child-process (that way, in the Task Manager, all sub-processes will share the name of your executable).
  7. Mono support has been improved across all platforms. Now uses a single assembly for all platforms and automatically loads Awesomium dependencies via ldd on Linux.
  8. Integrates all core changes from 1.6.3 (History API, Login Dialogs, Javascript Dialogs, etc.)

Also read...


  1. This is great!
    The only thing I’d love to see – improvements in font rendering on windows. Safari renders pages a lot better than chrome. And Chrome does in better than raw Awesomium. May be I missed something. Is there a way to improve rendering?

  2. Hey! The NET changes sound great. The closed source thing is a bit of a downside. How can we include quick and dirty support for Surface SDK (1 and/or 2). We need to translate at least taps to clicks. Will you consider native Surface support any time soon?


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>