With 1,087 commits in the past week, most of which were created for the Chromium project, it has been another average week. This week’s update will be brief considering I’m a bit short on time right now :).

There have been some interesting changes to form-support within WebKit in the last week. A bunch of new attributes are now available, like the form-attribute, as well as the formaction, formenctype, formmethod and formtarget attributes. Meanwhile, work on the framework for interactive validation support continues.

More progress has been made on supporting vertical text within WebKit. Support for vertical ruby has been finalized and lists now work vertically as well. Furthermore, repaint invalidation has been fixed and a number of bugs with the orientation of fonts have been solved as well.

Within Chromium’s about:flags page, support for click-to-play, experimental extension APIs and Snap Start has been added. For the sake of clearing up the situation around issue 61745 a bit: different from what news sites report, preloading pages in the background has not been implemented yet, and therefore it’s impossible to notice improved performance. Makes sense, right?

Other changes which occurred last week:

• Option elements for Chromium can now be hidden by setting the CSS property display to none.
• The accuracy of serialization of numeric input elements has been decreased, WebKit was too precise.
• The first steps towards exposing the synchronous implementation of File Writer have been made.
• Support for the HTML5 ruby elements cannot be disabled anymore.
• canvas.putImageData (canvas.getImageData (..)) will now do its job without losing quality.
• Support for multisampling has been added to the GPU’s drawing buffer.
• The selectionStart and selectionEnd properties will now report the right values for textareas.
• Parsing of various CSS keywords has been added for the content-property to fix out-of-flow counters.
• Two Web Timing interfaces have been renamed to match the specification. requestEnd has been removed.
• WebKit’s HTML parser will now provide the script column position to the JavaScript engine.
• CPU Profiling in Web Inspector will now survive navigation, making it easier to inspect.
• More fine-tuning and fixes for the Audio API, as well as landing the JavaScriptAudioNode files.
• Web Inspector will now also allow you to set breakpoints on clipboard, device and control events.
• In preparation of launching the Chrome Web Store, some textual enhancements have been committed.
• The usual bits of fine-tuning for Chromium OS have been present as well.

That’s it! Next week’s post will be a bit longer again.