Thanks for pointing this out. This does appear to only be happening for that page in Chrome, so I have pointed it out to our developement team to look into and fix.
We have just recently released this version (v3.0.5.1) in the last couple of days, so we're working through any issues such as this for a fix release to come out soon.