Is this one of the drawbacks of Chrome's insanely quick release schedule? We've seen the benefits, it's not surprising that there are some drawbacks.

I fail to believe that such a fundamental bug would have been in a major Firefox release, although stranger things have happened.