While it might not have been something of a priority to fix this. We are aware of the issue regardless, as we have a bug report of it in our internal bug database. While I can't promise it to be fixed in time for the next patch, it should get fixed eventually.