Please reference the following closed post.
This issue was never resolved, despite being acknowledged as a legitimate problem/issue/bug whatever you want to call it. In fact several versions later, Version 1.31.3.6868, the behavior still exists.
I must stress, as I did in previous replies, I am not as concerned over the lack of a solution to the problem as I am about the complete lack of any communication. I would like any update as to whether this problem has ever been escalated to devlopers or not.
