After a little more checking, I found that this bug first appeared in 2012 TurboTax and, as far as I know, has been present ever since.
