Is this going to be fixed some time soon? The issue tracker says fixed but still having this issue in 4.16.1!