@Matt if this bug has been around since 2.7, then one must assume that WP development considered the issue to be minor, in order to have not been fixed quite some time ago. Which leads to questions like: why is it considered serious enough now to warrant a fix with a new 2.8.x release? And if it warrants a new release now vs. just rolling it into a future major release, it makes it look like something more serious had been "back-burnered" when it shouldn't have been?