Fullscreen API, enhanced Element Highlighting and progress on Flexbox

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

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-alignflex-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:

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!

6 Responses to “Fullscreen API, enhanced Element Highlighting and progress on Flexbox”

Both comments and pings are currently closed.

BrianMB

August 29, 2011 at 10:54 pm

Wow, great update!

The element highlighting is well overdue.


I’m not sure I’ll enjoy those “sever sent events” though… ;)


lensco

August 30, 2011 at 9:17 am

Glad they finally implemented my bug for the element highlighting, but as far as I can tell they removed the color configuration from inspector.css – so they made it impossible to customize these colors with user css? Personally I think the borders around the highlights should go as they are rather confusing.


Jon Rimmer

August 30, 2011 at 9:54 am

Yeah, I agree. Borders around the highlights don’t really make any sense. Firebug’s highlighting is still superior in that respect.


skadate

March 24, 2013 at 10:18 am

I’m extremely inspired with your writing abilities as well as with the format to your blog. Is that this a paid subject or did you customize it your self? Anyway keep up the excellent high quality writing, it is rare to see a great weblog like this one nowadays..

Stop by my blog – skadate