An important comment on the bug from a Chromium employee [0] Hacker News crowd, let's please stop the "me too" party here, and please file separate bugs for separate issues (even if they're similar). Keeping the signal-to-noise ratio sane on this one raises the chances that it gets addressed :) So you can help by only commenting if you have technical comments on how to fix the problem in Chrome. It'd be a shame if we…
1. Have the problem
2. Take the time to voice their wish for a fix
Even the coolest bug will remain unfixed if only one person reports it.