Thanks for letting us know, we'll get this fixed in other browsers (we've been just looking at it in Safari).