See the last comment on the issue
Since this is fixed by clearing the browser cache, I'm marking this as resolved. If anyone feels strongly that Tapestry should have a better mechanism for preventing old JavaScript from hanging around after an app is upgraded to a newer Tapestry version (such as having the Tapestry version be part of the asset URLs), please open a separate ticket with the proposal.
