Hey Lesley,
Thanks for following up with us here.
I took a look at the bug report created f0r the original thread and it is still in our queue. It doesn’t look like it will be addressed in the next release since it was added after the scope for this release had already been defined. I can’t tell you exactly when this issue will be addressed however, we have a larger team dedicated to development with the goal of decreasing the timeframe that these types of bugs stay in our queue.
I apologize for the inconvenience. If you have any further questions, please don’t hesitate to ask.
Thanks!