Please reread your own comment.
I was replying to your incorrect comment and conclusion. I am not starting any flame war, but giving you an honest update and asking you questions why you arrived at the conclusion you did. If you had read my May 29th and June responses and finally my July 11th reply on this thread then you would clearly understand and see that it has been given attention and it is under investigation and actively fixed as best possible right now.
Feedback that is useful and often very helpful but to suggest that you stated what our priorities are is and that this bug is low is very presumptive to say the least.
Sorry you felt that my response was not correct but you are expected to read the thread thoroughly and see that there is activity here and you not being ignored. I am only interested in one thing, that is making this feature work with the highest quality I can.
I hope you don't abandon this product and even feature, because I have not fixed this on your timeline.
Thanks.
Steve