abarth

The fast path is much faster and handles the common case. The complex path is, well, complex, but it's the "all sing, all dance" path that handles all the difficult cases.

I'm one of the developers of threaded HTML parsing in WebKit. Threaded HTML parsing is only enabled in Chromium (for now). We're still working through the kinks. :)

Based on the discussion in the W3C, I would expect other browsers to implement "new Notification" rather than implementing the window.notifications factory object because the factory object doesn't really serve any purpose. We'd like to remove the factory object from WebKit eventually once folks have switched over to the unprefixed API.

You should really use "new Notification" rather than "createNotification" because "new Notification" will be supported by browsers other than Chrome:

http://www.w3.org/TR/notifications/#api

Something similar is happening to HTML5 in the W3C: http://blog.whatwg.org/html-and-html5

> I can't find out how to theme Chrome

A variety of themes are available in the web store: https://chrome.google.com/webstore/category/themes

This is fixed in manifest_version 2:

"A package's resources are no longer available by default to external websites (as the src of an image, or a script tag). If you want a website to be able to load a resource contained in your package, you'll need to explicitly whitelist it via the web_accessible_resources manifest attribute."

http://code.google.com/chrome/extensions/dev/manifestVersion...

See <http://blog.chromium.org/2012/02/more-secure-extensions-by-d...; for information about other security improvements in manifest_version 2.

CSP doesn't impose that restriction, but it's something we're changing at the same time:

"A package's resources are no longer available by default to external websites (as the src of an image, or a script tag)."

http://code.google.com/chrome/extensions/dev/manifestVersion...

Chrome also caches the compiled JavaScript in the HTTP disk cache. The biggest performance wins are for large scripts used by many web sites (such as jQuery).

This is the first release with a stable ABI:

"Applications compiled with version 0.5 of the SDK will work in Chrome 14 and future versions of Chrome."

http://code.google.com/chrome/nativeclient/docs/releasenotes...

That approach appears to provide an incentive for employees to leave so they can liquidate their holdings.

Here's the design document: http://dev.chromium.org/developers/design-documents/prerende...

The browser does download subresources, including images, scripts, and stylesheets. The new page visibility API is intended to help folks keep accurate web stats:

http://w3c-test.org/webperf/specs/PageVisibility/

The full details are here:

http://w2spconf.com/2011/papers/websocket.pdf

(Full disclosure: I'm a co-author of that paper.)

The Canary build goes out automatically without being looked at by a human, so there's a very real possibility that it will be unstable. Currently there's some strange crasher in the PDF viewer, for example.

You can install Canary "side-by-side" with another channel, so you can switch back to something more stable if canary goes pear-shaped.

Please consider reporting the bug so that we can fix the problem:

https://bugs.webkit.org/enter_bug.cgi?product=WebKit

We have a large number of tests, but sometimes we miss things. :(

The idea behind this approach is to simplify the maintenance of the copyright line and to encourage collective ownership of the code. I'm told that some open-source projects have conflicts about who's name appears in which files, but I've not experienced that first-hand.

That's correct. We're using leveldb as the back-end for IndexedDB in Chrome.