Actually if it's like this in 1.38 already (and possibly earlier) I see no compelling reason to rush this into 2.0, considering that tomorrow is release.
It's not even clear to me if this is even a bug (as on "not working as intended"). I surely never used that pref.