Peter Beverloo

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.

kurtextrem

Peter Beverloo

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

ainstushar

August 23, 2011 at 12:36 am

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.

[…] 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.) […]

Peter Beverloo

August 23, 2011 at 10:41 am

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.