Color input, the Network Information API and Chromium 20

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

1,104 changes landed in Chromium’s repository last week, whereas WebKit’s received 792. Highlights include Chromium 20, support for <input type=color> and re-landing of the vw, vh and vmin CSS units.

Chromium’s latest version number is the only number with more than one digit that can be written from base 2 to base 20 using only the digits 0 to 9: version 20. Highlights of Google Chrome 19 include support for the CSS calc() function, quote some updates to the Extension APIs and support for mutation observers.

A skeleton of Chromium’s Content Shell for Android landed last week, which is the very first step towards being able to build an Android .apk file containing Chromium. Meanwhile, work on supporting Password Generation is also progressing with some new constraints and a user interface for Linux.

Support for IndexedDB in Web Inspector’s Storage Panel is now available by default. Line-endings won’t be re-set anymore after editing a file, heap snapshot parsing has been significantly sped up and the shortcut for going to the previous panel has been changed. Development on supporting snippets is ongoing, as is support for device metrics emulation.

After having been rolled out, support for the vw, vh and vmin CSS units has returned to WebKit. Flexbox’ flex-line-pack property has been implemented and two bugs around the flex-pack property have been fixed. Replaced elements now box-reflect and vertical-align and more progress landed for the new Multiple Column implementation. Finally, CSS Exclusions’ shape-inside and shape-outside had their “wrap-” prefix removed, and now occur in the list of computed style properties.

Support for the Network Information API landed in WebKit, currently only enabled for the EFL port. The “preview” state of the Page Visibility API has been implemented and toggling the “disabled” attribute on a fieldset element will now also effect all form associated elements it contains. Verification for the Sec-WebSocket-Protocol header has been made significantly stricter, cross-origin behavior for XMLHttpRequests seeing redirects has been aligned with the specification, and  images will now have their error event fired when the CORS check fails.

Other changes which occurred last week:

If you’re one of the people interested in charting Dimitri Glazkov’s average arrival time in the office based on his daily good morning wishes to the #chromium IRC channel, Brett Wilson has the perfect solution for you: 6,143 indexed pages spread over 13 books containing all of 2011’s IRC conversations!

3 Responses to “Color input, the Network Information API and Chromium 20”

Both comments and pings are currently closed.


April 2, 2012 at 8:06 pm

Finally, input type=color! 😀 Makes me happy.


April 3, 2012 at 4:49 am

that’s a lot of work. thanks for sharing. keep up-.