Download extension API, composited canvas filling and PulseAudio

Published on August 22nd, 2011 in Google Chrome, Last Week, tech, WebKit. Version: Chrome 15

Last week brought another 1,205 changes; 465 to the WebKit repository, and 740 to Chromium’s. Highlights include a new extension API for downloads and fixed composited canvas filling for certain modes.

Within Chromium, stubs for an experimental download extension API have landed. The proposal aims to enable extension authors to offer features such as downloading all the images on a page, and deals with permissions and security concerns accordingly.

An announcement by the Android Browser team was made on the webkit-dev mailing list today in which they announced their intentions of improving collaboration with the WebKit community. The first two steps will be removing all current Android-specific code from WebKit and contributing a build bot to aid in long-term maintenance.

As for specification related changes, region invalidation and repainting now works properly. Canvas fill and fillRect have been taught how to deal with five more compositing modes, WebSocket’s CloseEvent now contains the code and reason properties and text input events for textboxes which may not contain text will now be ignored. Finally, three new CSS properties for CSS Regions were added and content within a region no longer is scrollable.

Two changes were committed by Jeffrey Pfau for the new XML parser, namely the document fragment parser and support for scripting within XML documents.

Other changes which occurred this week:

Among other areas, Accessibility, Document and Element related code now also switched to using the
abstracted LayoutUnit type for rendering positions. Another step closer to float-based rendering.
Web Inspector’s context menu now works properly when debugging remotely.
Long CSS edits in Web Inspector’s style pane will now be word-wrapped.
More work on implementing the bookmark page on the new New Tab Page has been done.
The focusin/focusout and focus/blur events now respect shadow DOM boundaries.
Another removed class from the editing system: webkit-indent-blockquote.
Dean Jackson now is a WebKit Reviewer! Congratulations!
Smooth scrolling has been enabled by default for Chromium on Mac OS X.
Plumbing has been done to start supporting the MediaElementAudioSourceNode component.
Plumbing has been done in WebKit to start getting scripted full-screen support to Chromium.
Several fixes have been made to get the Idle extension API working properly again.
A fast-path has been implemented to improve painting performance of tables with overflowing cells.
Multiple profiles on Mac are now enabled by default, and the profile avatar icon won’t show up
anymore unless the user actually has more than one profile.
Several measures have been taken to improve the performance of resizing canvases.
Scaling of iframes and framesets has been fixed.
Chromium’s component build now splits up to ipc and gl/compositor/surface libraries.
Support for headers and footers in printing for Chromium was added for Skia and Core Graphics.
Chromium can now output audio on Linux systems using the PulseAudio back-end.

And that’ll be all again.

9 Responses to “Download extension API, composited canvas filling and PulseAudio”

Both comments and pings are currently closed.

When does Smooth scroll come to windows?

Real Soon Now. It’s being worked on and will undoubtedly be enabled soon enough.

Love this website and amazing updates. Keep up the great work.

OFFTOPIC: Also, I am not a chrome dev and I don’t know the internals, but does chrome have any APIs that enable a developer to create an extension similar to Downthemall in firefox? Chrome’s default download manager isn’t good enough and I haven’t seen any extensions. I would love to see a speed graph, with TOTAL download speed of all my running downloads, the ability to pause and resume ALL downloads at the same time.

If you have any say in the chrome dev community, please bring this issue to light.

[…] a group of Googlers have announced on the WebKit-Dev group today (relayed by Google’s Peter Beverloo), the Android team is now committed to working more closely with […]

[…] Google announced that it will be removing the current incomplete Android-specific code from Webkit. Google also highlighted that “the Android Browser has come to share more and more code with Chrome (both WebKit and Chromium)” which drops the requirement for a separate build system for an Android webkit wbe browser as Google can reuse Chromium’s system now. There is no more need for a separate set of WebCore clients and embedder APIs, as the Android port shares a large part of the Chromium port code. According to Google, the Android layout tests closely match the results of Chromium for Linux. (Thanks to Peter Beverloo for the tip.) […]

ainstushar, I’m pretty soon that this will be possible with the new Download Extension API. It allows you to get the size, downloaded bytes and start time for each download.

[…] a group of Googlers have announced on the WebKit-Dev group (Source – Google’s Peter Beverloo), the Android team is now committed to working more closely with the […]

[…] de Google, que debatía con un nuevo desarrollador de Chrome llamado Peter Beverloo si se podría integrar o no Chrome en […]

[…] a group of Googlers announced on the WebKit-Dev group (Source – Google’s Peter Beverloo), the Android team is now committed to working more closely with the […]