Okay I'll see if I can apply that fix in a future update, thanks! It's probably a Chrome specific thing then.