It was in the release candidate.
It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first release candidate. This is covered in the article.
It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first release candidate. This is covered in the article.
It might have been HN, but it might not have been. (Surely other things have been fixed between RC and release without HN intervening.)