Web Audio API, script de-obfuscation, an updated UI and the contentSettings API

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

The Chromium and WebKit teams checked in a grand total of 1,496 changesets over the past 168 hours. Highlights include the availability for the Web Audio API on all platforms, script de-obfuscation in Web Inspector and a slightly updated user interface for Chrome 12.

Following the availability of the Web Audio API on Mac OS X, Kenneth Russell flipped the switch for branded Windows builds, after which Chris Rogers landed a patch making it work on Linux. If you’re on Windows, get yourself a Chrome Canary build, launch it with the “--enable-webaudio” flag and check out some examples! The commit has been reverted, but work is on its way to get the API back in.

The Web Inspector team has made some great commits again. Firstly, obfuscated source-code (such as a minimized jQuery) may now be cleaned up in the Script Panel by right-clicking on the content and selecting the de-obfuscate option. Undo and redo has been implemented for the text editor, accidentally switching panels during live editing using certain shortcuts has been fixed and the resources panel can now display raw HTTP-headers. Finally, early steps have been taken to move the Detailed Heap Snapshots processing into workers.

One of the problems the prefetch relation for <link>-elements has, is that the linked file will be loaded in WebKit at a very low priority. In order to offer authors a way to preload resources which will be used on the current page, Gavin Peters has implemented the “subresource” relation.

As for specification compliance, a regression related to the ACID3 test has been fixed meaning that it will render pixel-perfect again. The Blob’s slice method has been renamed to Blob.webkitSlice, while also having its semantics change to mimic Array.slice. Simon Fraser has begun with improving WebKit’s border mechanisms, initially by improving the logic used to compute the inner radii on curved borders. Stay tuned..

WebKit’s Content-Security-Policy is now aware of the “self” source and will block string arguments to setTimeout and setInterval unless the “eval-script” option has been set, as they would evaluate the string internally. It is now also possible to define what sources media elements can load from, using the media-src directive.

Other changes which occurred last week:

  • Following the skeleton and the WebKit define-switch, compiling the LevelDB back-end for IndexedDB has been enabled for Chromium.
  • The SH4 JIT for JavaScriptCore has been both finished and enabled by default for Qt!
  • WebKit2 now supports searching text within PDF documents using the default Find in Page.
  • Composition propagation has been implemented for object-elements and framesets.
  • ArrayBuffer responses for XMLHttpRequest in Safari on Windows have been enabled.
  • Good news for WebKit reviewers with an iPad: the review tool is now compatible.
  • A bunch of new icons have been committed for Chrome 12′s user interface, being a bit more gray.
  • The SVG lighting filters have been sped up four times for ARM-processors.
  • Speech input has been disabled for readonly and disabled form input fields.
  • Chromium’s compositor will now tile larger (>512 pixels) content and image layers.
  • A unified Quota API will now be exposed from WebKit if it’s built in a certain way.
  • The Qt port has implemented mime-snifing based on Adam Barth’s IETF proposal.
  • A flag has been added so development of a Page Visibility API in WebKit can begin.
  • The experiment with moving the caret by word in visual order received two follow-ups.
  • Chrome’s text anti-aliasing has been fixed when text renders with a shadow.
  • The enableReferrers and enableHyperlinkAuditing options have been added to a new contentSettings extension API for Chromium. Looks promising.
  • A user interface has been added to control Virtual Private Networks in Chromium OS.
  • The Print to PDF dialog for Chrome’s Print Preview feature will now suggest a filename.

And that’ll be all again!

5 Responses to “Web Audio API, script de-obfuscation, an updated UI and the contentSettings API”

Both comments and pings are currently closed.

Chris Rogers

April 19, 2011 at 2:28 am

Sorry, but the Web Audio enable has been reverted for now. We’re getting close though :)


Peter Beverloo

April 19, 2011 at 9:18 am

Ah, too bad. I’ve updated the post with that information. It did cause quite some crashes for me, both in Canary as in Chromium.


Peter Kasting

April 19, 2011 at 9:55 am

Your first bullet point looks like it’s missing a word or two (compiling what?).


badboy_

April 19, 2011 at 10:03 am

So now that the Web Audio API nearly landed on all platforms when do we get support for different sound systems on linux? With my PC using OSS (Open Sound System) I can’t test any of the great new features such as HTML5′s and tags due to the lacking of sound :(


Tsvetan

May 23, 2011 at 3:39 pm

It seems that subresource link rel does not work(atleast for Chrome 13.0.767.1 dev) – in the network panel of the Dev tools get request for the suvresource always fails.