When Google launched the Ajax Libraries API in May, Dion Almaer noted that it might be possible for browsers to further improve performance of applications using this API:

If we see good usage, we can work with browser vendors to automatically ship these libraries. Then, if they see the URLs that we use, they could auto load the libraries, even special JIT'd ones, from their local system. Thus, no network hit at all!

A great idea, but as far as I know not one that any browser has currently taken up. When Google announced Chrome in September I wondered if they might be the first browser to support such a feature. Today I finally got around to testing the latest Chrome using Wireshark and discovered that it doesn't yet do this, at least not for the latest jQuery release.

So I've taken affirmative action in the spirit of John Resig's recent advice and filed a feature request at the Google Chrome support site.

I recently ran across some curious JavaScript behaviour. Nothing new there, but I was slightly annoyed to see that my handy reference book hadn't given me any clue about the inconsistent way in which different browsers handle the Array.splice method. O'Reilly's JavaScript: The Definitve Guide (5th edition) is usually pretty good at pointing out any browser compatibility issues.

But after digging some more, I was even more confused to find that the book seemed to be wrong in its description of the method.  ...read more »