Last week brought 649 commits to the Chromium repository, and 575 to the WebKit one. Among the changes are support for auto incrementing keys for IndexedDB and interactive validation which will now be available by default in Chromium. The Web Inspector team has been active again as well!

After a few weeks of behind-the-scenes work, Web Inspector has received some very interesting updates again. Following auto-completion for properties, many values will now be suggested and completed for you as well. The heap snapshot table may be sorted again, CPU profiles will survive refreshes and using the console.trace method won’t cause a crash anymore. Web Inspector has also been taught application/x-font-woff as a valid MIME type for WOFF fonts.

Furthermore, a change has been committed which is a first step in supporting breakpoints on arbitrary positions on a line, which would be convenient for compressed scripts. Additionally, UglifyJS will be assisting in that as well, considering it’ll be included with WebKit in preparation for a script beautifier feature!

There have been quite a few specification-related updates this week as well. Interactive Validation has been enabled by default for Chromium, color changes in <select multiple> will be visible immediately and clipping backgrounds to the content-box now is a possibility. Furthermore, keygen elements won’t identify themselves any more as select elements. Mozilla’s requestAnimationFrame has been implemented, including on the Chromium side.

As for HTML5, two new form-related events have been implemented: onformchange and onforminput. Per the request of Jeremy Keith, datalist elements will be visible by default again, and uncaught JavaScript exceptions will now trigger the onerror event on the window object.

One performance-related change by Stephen White is the implementation of accelerated path drawing and clipping for the 2D Canvas GPU-path, done using a simple curve interpolator and the GLU tesselator. It speeds up Microsoft’s Galactic demo by three to five times —quite impressive.

Other changes from last week include:

• More efficient, in-browser thumbnail generation is now available via a command line flag.
• The --remoting flag and setting in about:flags are now available for all platforms.
• Basic printing routines have been implemented in the WebKit2 API.
• Some revalidation checks have been removed from the pre-rendering conditionals.
• The languages and spell-check pages are now available in the DOMUI Settings for Chromium.
• Style sharing optimizations have been improved, with 25-40% of the styles being shared.
• An onBeforeRetarget callback has been introduced to the Web Navigation Extension API.
• Happy New Year to Chromium’s about:version page!
• The state of  the set about:flags has been moved out of a user’s profile.
• The about:version page in Chromium now reports the used WebKit branch and revision number.
• Various matrix multiplications will now be done in the in a column-major order.
• The OES standard derivatives WebGL extension has been implemented in WebCore.
• The IndexedDB implementation now is capable of handling auto incrementing keys.
• Regular Expression objects in JavaScript aren’t callable anymore in Safari.
• Support for YV16-video frames has been added to Chromium’s WebKit port.
• In preparation of accelerating more drawing via the GPU, Chrome has updated the Skia version.
• Enforced throttling for URL requests has been disabled in Chromium, pending further analysis.
• Loads of JavaScript stability fixes by Apple’s JavaScript team.
• Password input fields will now show a warning when caps-lock is enabled, on GTK WebKit.
• The -webkit-mask-* CSS properties can now be rendered using accelerated compositing.

And that’d be all again! Be sure to have a peek at this week’s update on the WHATWG blog, with topics like a proposal for XSS mitigation in browsers and a Change Proposal for a muted attribute for media elements.