3 ms·
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 (Chrom
by magicalist 12y ago
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).
- thebear 12y agoThanks, I have updated the blog post accordingly. There is a conspicuous note at the top now saying the problem will be fixed in version 38. I think the blog post still makes sense, as it will be a while for the fix to become effective for everybody.