Another 1,301 patches landed last week, 464 at WebKit’s and the rest at Chromium’s, bringing highlights such as the Fullscreen API in Chromium, colored highlighting for Web Inspector and removed code from the Android port.

James Kozianski landed support for the Fullscreen JavaScript API in Chromium, which will be enabled when the --enable-fullscreen command line flag has been supplied. Within WebKit, the API will now always be included in the build and had its internal APIs exposed.

Within Web Inspector, an element’s margin, padding and content will now be drawn using different highlighting colors, making it much easier to see why certain content may be out of line. The extension API has been updated with the ability to access page resources, and more progress has been made in the effort to support compiling the front-end using Closure Compiler.

As for progress on the updated Flexible Box implementation in WebKit, Tony and Ojan landed patches adding support for the flex-align, flex-order and flex-pack CSS properties, switched the default preferred width of the flex() function to 0px per a specification update, handling the margins of child elements and behavior when min-width and max-width are used for flexible elements.

Accuracy of the implementations of supported specifications has been improved again as well, with Alexandru Chiculita fixing two issues with floating elements, while Mihnea Ovidenie fixed getting the client rectangles for content flows. Absolutely positioned layers won’t overlap its parents anymore when a breaking element is in between, Event constructors got implemented, then reverted, then implemented again, text-overflow now works properly for button elements, layout for :before and :after content used with tables has been fixed and a createObjectURL method has been added for the MediaStream API.

Adam Barth and Steve Block removed, as promised, the Android port from WebKit. A build slave for testing WebKit’s Chromium port on the Android OS was added as well, but hasn’t been activated yet.

Other changes which occurred last week:

• Chrome extension docs have been updated with Chrome 14’s new APIs.
• A proper keypath parser following the IndexedDB specification has been added.
• Support to pretty-print the XML tree has been added to WebKit’s new XML Parser.
• Momentarily revealing the last typed character for password fields now is supported natively.
• Chromium’s renderer will no longer crash when the about:gpucrash page is loaded.
• Incremental linking of WebKit for Chromium’s component build is now supported.
• WebKit’s GTK port has switched to using GTK+ 3.x by default.
• An audio source provider has been added for Media Elements, for use with the Web Audio API.
• Chrome’s commit queue has been taught the Drunk Manager Algorithm.
• The PulseAudio implementation in Chromium now supports Surround Sound.
• Accelerated 2D Canvas has been disabled altogether for Linux installations.
• Closing a tab while pressing the option-key will now close all other tabs on Mac OS X.
• More new libraries for the component build: ppapi_proxy.dll, ppapi_shared.dll and libffmpeg.so.
• Typed URLs in the Omnibox will now be synchronized with your account by default.
• A sample webRequest extension has been added, promoting funny dogs.
• Five new DLL libraries have been blacklisted given their contributions to Chrome crashes.
• The remoting-it2me.zip file has been added for Linux and Mac distributions.
• Furthermore, Mac has been given a host policy for connections used by Remoting.
• Files in Chromium OS’ file manager will now be sorted by date, descending, by default.
• Clearing cache, cookies, downloads, form data, history and password may soon be done via
  the experimental chrome.experimental.clear Extension API!
• Toggling various privacy-sensitive may soon be done via the experimental Privacy API!

And that’ll be all again! Patches to look out for this week include the ability to receive binary WebSocket messages as Blobs and the addition of CORS support for Server Sent Events!