Gardening tools, multiple-profiles and lots of changes in Web Inspector

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

Much later than usual, but live from Mountain View this time! Last week brought 838 updates, 468 at Chromium’s, the rest at WebKit’s. Highlights include work on a new tool for WebKit Gardeners, many updates for Web Inspector and two more parsing patches for Adobe’s CSS Regions.

Adam Barth started to work on a new Gardening tool for WebKit, called garden-o-matic. Gardening is the act of making sure that the build tree remains green, ensuring there are no unexpected test failures, etcetera. The idea is to provide a dashboard to developers allowing convenient access to actions like reverting changes, finding unexpected failures and the build which made them fail.

Now that WebRTC has landed as a Chrome dependency and work on implementing several related features in WebKit is well on its way, Magnus Flodman landed an early implementation of the Media Stream Manager. This Manager will coordinate between WebKit’s API, permissions, WebRTC and of course your camera and microphone, ensuring that the feature will work smooth and secure.

The multiple profile feature has received quite some work as well this week. The setup UI for a new profile has been implemented, deleting profiles now is a possibility, the displayed avatar can be customized and will contain most profile-related options. Finally, it has been enabled by default on the Views UI, presumably Chromium OS.

An incredible amount of changes happened for Web Inspector last week. You can now drag and drop elements and other nodes in the Element Pane, a new settings panel has been added, and cache and cookies can soon be removed via the Network Panel. Speaking of which, you can now also search in the Network Panel, albeit still limited to filenames and paths.

The specificity of !important properties for the Inspector has been fixed, links to stylesheets will now open in the Style Panel, multiple resources will be shown when a URL is referred to multiple times and requests made by plugins will be shown in the Network Panel. Finally, it’s now clearer how to add a new style rule and adding CSS properties will no longer result in messy CSS rules.

As for specification related updates, the value property of an indeterminate progress bar will now return zero. A change event will be triggered when the selected files of a file input change, column-break-inside: avoid has been re-enabled and more key-bindings have been added to range inputs. Furthermore, parsing capabilities for the flow and from-flow properties, as part of their CSS Regions proposal. Finally, more work on switching WebKit’s Render Tree to a float-based representation has been done.

Other changes which occurred last week:

And that’ll be all! I will be in the Mountain View area until July 23rd and will attend Open Web Camp III (thanks, John Foliot!). If you want to meet up, feel free to drop me a note.

4 Responses to “Gardening tools, multiple-profiles and lots of changes in Web Inspector”

Both comments and pings are currently closed.


July 14, 2011 at 1:25 pm

Hi Peter. As always, thanks for the great amount of useful information!

Something I have always wanted to see in Webkit Inspector is an ability to temporarily disable loading of some network resources. For example, if you happen look at the Network panel and you see a resource is potentially blocking others, you could just disable it temporarily and refresh to see if it really did that and how much it affected your page loads.


Peter Beverloo

July 14, 2011 at 4:07 pm

Hi Kai, while I can see use-cases for the feature itself, I’m not sure how feasible it is right now. You can file a bug on or explaining your desired feature together with (preferably) one or two use-cases, and someone of the Web Inspector team will have a look.


July 19, 2011 at 5:51 pm

Just a small clarification. The Qt port has already supported shadow blur for a while (see The blur code that I implemented was then refactored and polished to be used by other ports (notably Mac, for Safari). The recent change was merely to converge these ports to use the same cleaned-up version of the code.

Peter Beverloo

July 19, 2011 at 10:25 pm

Alright, thank you! Blur code has undergone quite some changes recently, so it’s a bit hard to keep up.