CSS Filter Effects, Extensions Settings API and seamless GCF updates

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

Last week, 539 changes landed in WebKit’s repository and 824 landed in Chromium’s, totaling up to 1,363 changes. Highlights include start of the CSS Filter implementation and lots of removed code within WebKit.

The Extension Settings API has been implemented for Chromium! This new API will allow you to specify settings for your extensions which will then be synchronized to the user’s Google Account, similar to your bookmarks.

Google Chrome Frame has been updated to no longer show a security prompt after it has been updated without re-starting Internet Explorer. This improves the user-experience for those stuck to IE quite significantly.

For those using Web Inspector on Windows, saving the timeline data is now working again. Callbacks originating from requestAnimationFrame will show up in the timeline panel, and the Metrics sidebar pane for the Elements panel will now be drawn at all times. Outlines have been removed from this pane as well, considering they’re not part of the box region.

Two more tests from the CSS 2.1 test-suite are now passing, getting a non-premultiplied image from a WebGL object will now yield the expected result and positioning issues with :before and :after pseudo-selectors used with tables have been fixed.  Finally, Apple finally implemented Function.prototype.bind for their JavaScript engine, and also aligned the String.prototype.split implementation with ES5!

Quite some cleaning up has occurred within WebKit as well, for one, the BREWMP and HAIKU ports have been removed as they weren’t being maintained anymore. similar to the implementation of WCSS. Several features, such as Application Cache and Server Sent Events have been enabled for all ports, and clearing of other miscellaneous compile-time flags started as well.

As for new features, Dean Jackson announced to start implementing the CSS Filter Effects, an effort led by the SVG and CSS Working Groups, enabling effects such as blur and drop shadows to occur on a page. Besides the implementation itself, investigation will be done as to enabling the effects to be animated and to be  accelerated.

Other changes from last week include:

  • The chrome://settings/extensions page has now officially taken over from chrome://extensions.
  • The Console Extension API for the Developer Tools has now been exposed to extensions.
  • The team-page on WebKit’s website will now be auto-generated from committers.py.
  • Performance improvements of 1.4%, 4%, 1.4% and 2% for Apple’s JavaScriptCore engine.
  • Corners of elements being manipulated using CSS 3D Transforms will now anti-alias correctly.
  • Redrawing the dirty parts of a large table has been optimized by adding additional caching.
  • Similar to Chromium, using OVERRIDE and FINAL annotations in code is now possible in WebKit.
  • Apple seems to be interested in using the Web Audio API, as they’ve added run-time settings for it.
  • Clicking backspace to merge a header with a paragraph won’t produce a span element anymore.
  • The Qt port has started implementing the JavaScript Full Screen API.
  • Implementation of DOM Mutation Observers seems to be starting in WebKit.
  • Animating the alpha value of a composited layer within Chromium is now possible.
  • Preparations are being made to move Grit to its own open source project.
  • An entry in about:flags has been added allowing people to disable WebGL.
  • Chromium on Mac OS X systems has now switched to using Skia as the default graphics layer.
  • The Image Gallery has been made more ribbon-like for Chromium OS.

And that’ll be all again.

7 Responses to “CSS Filter Effects, Extensions Settings API and seamless GCF updates”

Both comments and pings are currently closed.

Nathan Guenther

September 27, 2011 at 4:09 am

Still no twitter.com fix