Last week in WebKit:
Unregistering protocol handlers and improved input accuracy

Jun 11, 2012

by

This update considers all of 587 last week’s commits until revision 119951.

Web Inspector’s pretty print feature now respects the indenting preferences. Only the root domain will be expanded in the Sources and Scripts Panels and links will be opened by default in the Sources panel, falling back to either the Resources or Network panels.

Zero is now a recognized number again for numeric input fields. Rendering nested flexible box objects has been fixed, the “order” property now accepts a number rather than an integer and more CSS 2.1 issues have been fixed.

Besides registering protocol handlers, they can now be checked for existence and unregistered as well. The imageSmoothingEnabled setting for 2D Canvas contexts will now apply to patterns as well, client rectangles for frames in scaled pages will return the right values and the Pointer Lock implementation gained support for the change and error events. Finally, a build flag for the Undo Manager has landed.

The Blob constructor now accepts ArrayBufferView instead of a normal ArrayBuffer for its constructor’s parameter. Elements with an empty string as it’s “itemprop” value won’t be listed in Microdata’s properties list anymore and several SVG features now report to be supported through DOMImplementation.

After some more intermediary steps, Yoshifumi Inoue introduced the new Decimal type for an input’s value properties, fixing rounding errors in number and range input fields.

Other changes which occurred last week:

  • Duplicated Content Security Policy directives will now display errors in the console.
  • The “target-DensityDPI” viewport meta value will no longer be recognized by WebKit.
  • Wins of 3% on Kraken and 3% on v8 for the JavaScriptCore engine.
  • Render Nodes lost 8 bytes of weight, saving up to 2.6 megabytes when viewing the HTML5 specification.