Add me to the list of users who have encountered this issue.
I started a Support Chat with a member of the Adobe Support Staff concerning a totally different bug I've encountered. When we were unable to resolve the issue, we found a few work arounds. I asked them if this was likely something Adobe would look into, or if it would go untouched because we had discovered a successful work-around to my problem. I was told that they would address this with the programming and debugging staff, themselves. I'd like to think that this error (one of several on my list I'd like to address in other Support Chats) will be addressed in the next batch of bug fixes. I hope this info helps, or at least gives anyone else who is encountering this issue hope for its resolution.
I think the best approach would be to open a Support Chat Ticket (when you have ample time, because sometimes it can take a while to get through the whole process), and hash it out with the Support Staff. In your conversation, ask if they will be addressing it with those who can do something about it (i.e. Programming/Debugging staff.)
I'd love to think that the squeaky wheel will definitely get the grease, in this case. The more users that report this and go throughout the Chat process, the more likely we will see this issues resolved.