Tab Sizing, String Values for IndexedDB and Chrome 21

Published on in Google Chrome, Last Week, tech, WebKit. Version: Chrome 21

1,693 changes landed last week, 650 in WebKit’s repositories and 1,043 in Chromium’s. Highlights include Chromium 21, support for the tab-size property and strings instead of constants for IndexedDB.

Web Inspector’s search box supports CSS selectors again, JavaScriptCore timers will now show up on the timeline and a context menu has been added for tabs.

Text decorations, such as underlines, will now be rendered for text in :first-line selectors. Implementation of the :first-letter selector was aligned with the specification. Eric landed stylesheet inheritance support for seamless iframes, as well as the ability to inherit styles from their parent iframe.  The RadioNodeList interface is now supported, background-size is now part of the “background” shorthand and, albeit disabled, the <intent> element landed.

IndexedDB now uses strings instead of numeric constants. Violation reports generated by Content Security Policy now also include the referer, original policy and the URL which got blocked. The File System API is now able to deal with cross-file system operations, widths and heights are now exposed for <input type=image> images, and the offsetLeft property was broken when used together with CSS Columns.

WebKit has also gained support for the tab-size CSS property. This property, which is also supported by Firefox and Opera, allows you to define the number of spaces a tab should be equal to.

Included among other minor updates on the WebKit website, the conditions under which the WebKit trademark can be used are now available on the Mac OS Forge website.

Other changes which occurred last week:

An exciting thing to keep an eye out for in the upcoming weeks is Luke’s work on bringing CSS Variables to WebKit, the announcement for which has already been made!

4 Responses to “Tab Sizing, String Values for IndexedDB and Chrome 21”

Both comments and pings are currently closed.

Half a megabyte of memory was saved by Andreas when viewing the full HTML5 specification.

Please make happen!

Do you think Chrome will ever migrate to webkit2 ?

Peter Beverloo

May 15, 2012 at 8:52 pm

Do you think Chrome should?

The most important part of the WebKit2 API is to provide a multi-process architecture, which is an alternative to what Chrome already does.

Andreas Kling

May 15, 2012 at 11:04 pm

@Mathias: That site would just be this image:

No matter how skinny we get, we’ll never be “done” as there are always more awesome memory optimization around the corner. 🙂