As noted in the bug, the fix went into Chrome 38, currently in beta.
I don't have beta installed, but I can confirm it's fixed in dev channel and Canary (Chrome 39).
I don't have beta installed, but I can confirm it's fixed in dev channel and Canary (Chrome 39).