Guys this posting by bob gave us a clue that the fix to the problem will be in MC30 and not MC29
I don't think you should be able to get it behind the UI with 30.0.10.
Had you updated to that?
However, extensive testing revealed that the problem is not restricted to the Mac Platform; although it is harder to induce it also happens in Windows. In addition, it is not restricted to MC29, not only did I encounter the same "strange behaviour" in MC24, 25, 26, 27 & 28.
I also discovered that the problem was more extensive than had been reported so far, I discovered several different, sometimes unconnected, ways of inducing the behaviour.
For some very valid reasons Matt and Bob decided to take a "step by step" approach to developing/implementing a solution, on all platforms, as a means of avoiding "regressive behaviour", one change to an area of the tag window code having a detrimental effect elsewhere in the tag window.