3 ms·

A link to the reported bug seems missing?

• DannyBee 12y ago
  A little searching finds someone else (AFAICT) reported what i believe is the same bug as well: https://code.google.com/p/chromium/issues/detail?id=412640 https://code.google.com/p/chromium/issues/detail?id=412640 It was responded to immediately, tracked down, and fixed in M38.
  • deleted 12y ago
    [deleted]
    • 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 ago
        Thanks, 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.