A: 

We had the same problem - it's definitely a bug in prototype.js 1.6.0.x. Upgrading to 1.6.1 fixed it.

Sava Chankov