Well, he did swap out the client-side and it worked, so that's rather indicative of it not being a server-side problem. Not entirely given, it could be that Ch

Well, he did swap out the client-side and it worked, so that's rather indicative of it not being a server-side problem. Not entirely given, it could be that Chrome happens to implement erronous or non-standards-compliant behaviour which just so happens to match up with the erronous or non-standards-compliant behaviour of the server, but that's starting to get a little far-fetched.