Porting from v1.6 Beta B to v1.6 RC1

API Changes

In WebCore

  • Modified: The parameters for the WebCore constructor have changed-- it now accepts a single config parameter, see WebCoreConfig.
  • Added: New member method WebCore::clearCookies.
  • Added: New member method WebCore::clearCache.

In WebView

  • Modified: WebView::resize now offers an option wait for a full repaint (this prevents flicker after resizing).
  • Removed: WebView::zoomIn and WebView::zoomOut have been removed (use WebView::setZoom instead).
  • Added: New member method WebView::setZoom.
  • Added: New member method WebView::setResourceInterceptor.
  • Added: New member method WebView::getResourceInterceptor.
  • Added: New member method WebView::pauseRendering.
  • Added: New member method WebView::resumeRendering.
  • Added: New member method WebView::isLoadingPage.

In FutureJSValue

  • Added: New member method FutureJSValue::getWithTimeout.

In RenderBuffer

  • Modified: RenderBuffer::copyTo is now declared as const so that you can use it with the result of WebView::render.
  • Added: New member method RenderBuffer::saveToPNG.
  • Added: New member method RenderBuffer::saveToJPEG.

New class: WebCoreConfig

  • All configuration options for the WebCore have been wrapped up into a neat new class, WebCoreConfig.
  • You can now configure proxy settings, set global CSS styles (for stylizing scrollbars, among other things), disable cache, and more.

New classes: ResourceInterceptor, ResourceResponse, and ResourceResponseMetrics

  • You can now register a ResourceInterceptor with a certain WebView to intercept requests for resources. This is useful for implementing your own custom resource loading back-end and for monitoring resource loads.

Bugfixes and Other Notes

  • WebView::executeJavascriptWithResult is now fully implemented.
  • WebCore::setCustomResponsePage is now fully implemented.
  • WebView::getDirtyBounds was not returning the correct values after a scroll operation. This has been fixed.
  • Calling WebView::executeJavascriptWithResult or WebView::destroy from a WebViewListener callback caused a crash due to re-entrancy issues with WebCore::update. This has been fixed.
  • A new "folder" dock icon was previously spawned for each WebView render process on Mac OSX. This has been fixed.
  • WebView render processes were not exiting properly upon destruction of the hosting WebView. This has been fixed.
  • WebCore was not shutting down cleanly causing leaked memory and cache/cookies to ocassionally not be saved to disk. This has been fixed.
  • Passing Javascript values with an "Object" type back to the application via a Javascript Object callback previously caused the WebView render process to crash. This has been fixed.
  • Links that normally open in an external window were not properly being routed to WebViewListener::onOpenExternalLink. This has been fixed.