Not sure why this is big news, big enough to be in the #1 spot right now. From reading the comments on the bug, it seems to be an issue that's hard to reliably reproduce, and -- despite how simple it sounds from the editorialized HN title -- it involves interactions between different parts of the browser, and it's hard to track down and fix.<p>Nonetheless, there are some proposed fixes, and I expect a near-future release will have one of them.<p>This isn't that stereotypical "simple bug has been sitting around unresolved for years because (arrogant|understaffed|uncaring) developers can't be bothered" story that is unfortunately all too common in software (and not just open source software -- we just don't get to see it on a public bug tracker when it's in a proprietary product).<p>This is the process <i>working</i>.