It is fixed in our builds at work, however it simply did not make it into the current patch. But yes, we are aware of it and it should be addressed in the next patch - I have no ETA on when that patch will arrive.