Content Shell, Shadow DOM and Emulating Screen Sizes

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

Last week brought 563 new commits in WebKit’s repository and 709 new commits to Chromium’s, totalling up to 1,272 changes. Highlights include a content shell for Chromium and work on emulating screen sizes.

Chromium’s content shell for Linux-based systems was announced on the chromium-dev mailing list on Friday, sharing the news that it’s now usable for day-to-day WebKit development. It uses Chromium’s content module but leaves out other parts of the browser, so it’ll be significantly faster to compile and run.

For free-flow HTML editing in the Resources Panel of Web Inspector, revisions will now be tracked. Unsafe cross-origin requests will now show a stack trace in the console, making them easier to track down and content in iframes won’t appear to be in the same document anymore when using the DOM Viewer. Finally, a screen-size emulation back-end has been implemented, which will eventually allow you to emulate mobile device screens!


The -webkit-cross-fade will now report the intrinsic size of the background, fixing rendering when the background-size property is being used. Baseline grid alignment has been implemented, as have the text-overflow property for input fields and parsing for the custom() function of CSS Shaders. Painting background colors for regions has been re-enabled, and regions will now be exposed to the DOM.

WebKit’s Device Orientation implementation has been updated with the absolute property, which indicates whether the angles in the event are absolute. The abort() method for Application Cache has been added, as has a constructor for MediaStream accepting a collection of MediaStreamTracks. A window’s innerWidth and innerHeight properties won’t be affected by page scales anymore and drop and dragend events will now be issued for contentEditable elements.

Finally, the first significant patch in exposing the Shadow DOM to JavaScript has landed in WebKit! Minor as it is right now, it’ll pave the path to implementing the rest of the specification.

Other changes which occurred last week:

Finally, be sure to take a look at HTML5 Please, a new website sharing recommendations about which features of the Web Platform can be used today!

3 Responses to “Content Shell, Shadow DOM and Emulating Screen Sizes”

Both comments and pings are currently closed.

There should be a single-page website dedicated to printf’s memory improvements, with pretty charts and everything. “Are we memory-efficient yet?”


Michael P.

January 24, 2012 at 7:34 pm

Do you know if the bullet

The headers and body of HTTP requests will now be merged if the total length is <1400 characters.

is the same as "3. Use TCP Fast Open (TFO)" referenced in the "Let's make TCP faster" blog post from yesterday (http://googlecode.blogspot.com/2012/01/lets-make-tcp-faster.html)

Thanks.