No, the ticket is still far down in the backlog. It doesn't look like the issue has been encountered at a large scale so it's been marked as a low priority. With everything else being worked on for 8.3 I would not expect this to be fixed anytime soon.