With 901 commits at WebKit, and 1,298 at chromium’s, last week boosted up to a massive 2,199 changes to the repositories. Highlights include a that WTF no longer is part of JavaScriptCore, a new image-set() CSS function and SPDY/3 which can now be enabled through about:flags.

Following much discussion and preparation, including e-mail threads going back more than a year, Eric Seidel moved the WTF (Web Template Framework) code out of JavaScriptCore. It initially settled there in 2005 as the kxmlcore directory, after which it got renamed to WTF in 2006 as many more useful classes had been included there.

JavaScript files and stylesheets will now be editable by default in Web Inspector’s Resources Panel. Highlighting of SVG root elements with a custom viewbox has been fixed and Source Maps may now be defined inline.

An initial implementation of the image-set() CSS function landed in WebKit, as was proposed for the CSS Images Level 4 module last month. Mixed percentage and absolute combinations for calc() may now be used for masks, background positioning and image sizing, Hyatt is working on the new Multiple Column implementation and fieldsets won’t stretch to minimum intrinsic width anymore if an explicit width has been specified. Besides various other Flexible Box Layout changes, the flexing algorithm got updated.

The crossorigin attribute may now be specified on script elements, causing WebKit to apply the Cross-Origin Resource Sharing policy on script elements as well. Three DOM-mutating JavaScript errors have been updated to align with the DOM4 specification and WebSocket’s Sec-WebSocket-Accept may not occur multiple times anymore.

Other changes which occurred last week:

• The default WebSocket version to use for WebKit ports has been changed to RFC 6455.
• While still completely disabled by default, CSS Shaders can now be compiled for Chromium.
• The style sharing optimization can now be applied to elements with style attributes as well.
• Support for “magic” iframes within WebKit has been removed.
• Several getters have been added to the chrome.browserAction and pageAction APIs.
• The Chromium Android builder on the main waterfall now builds all of WebKit.
• Tab synchronization in Chromium is now enabled by default for all platforms.
• The user interface for <input type=color> landed in Chromium, though is still disabled.
• William Chan wrote an excellent article on DNS resolution in Chromium, a flag for which now landed.
• The topSites API no longer is experimental and a new experimental offscreenTabs API has been added.
• Threaded animation for WebKit’s compositor has been enabled by default on Chromium.
• SPDY/3 and the SPDY flow control can now be enabled on the about:flags page.

Finally, if you have interest in Adobe’s recent work on WebKit, they recently hosted a hackathon which yielded some interesting results. It’s a good read!