> This is likely a bug but I wanted to confirm others having > the same issue before listing it as such. Looks like the problem is caused by a bug in our JavaScript support. Thanks for reporting it! Ken