This was a cut-and-paste error in 47145f51. Thanks to @MattiasErikssonAxentia for the patch and test-case!