Comment by elboru

I don't think this was a single developer mistake (that would be easy to spot), instead this was a solution for a problem so it was a requirement for the new update.