Thanks for the heads up. For what it's worth, it appears that it was a problem with the version of AngularJS we were using (1.2.3). When we next push updates to the site and upgrade Angular, this problem should be fixed.