Not sure if my comments have been mentioned yet in this thread, but here's my 2 cents:
I got off the phone (today) with Apple Support and here's how it went.
I verbally described the situation and I CAN 100% reproduce it.
It's tough to describe in text, but here we go:
Here's the process:
- Activate any other window (any app or even have the desktop as the active element) so that Messages is in the background showing as inactive.
- Then, activate the Messages window by taping (and releasing your finger from the trackpad) just at the upper part of the window. Anything that is blank area above the text and search fields.
- Then, move your cursor to anywhere on the screen (even outside the messages window...while the Messages window is still active but you have not tapped or scrolled or anything else).
- Result: the Messages Window will align itself such that the top area of the Messages window justifies with where every you have tapped.
- This method will reproduce the bug 100% of the time.
Notes:
- Tapping and holding with the trackpad will not activate the window or cause the bug to occur.
- Tap/hold by physically pressing down on the trackpad (click+drag) will not reproduce the bug, only by tap release to active, then moving cursor and tapping a again.
- I first noticed this bug because i tap at the top of any app window to active it since sometimes tapping in an editable field or an area where there is an active element will sometimes activate that element creating a result I don't want. For example, if you have the messages window inactive and tap in an area where your active chat contacts are (even if inactive at the time) to active the window it will subsequent activate that conversation, not the currently visible one.
- As stated in more detail below, using a mouse or keyboard shortcuts will not reproduce the bug.
- Also, "tap to click" must be turned on to reproduce the bug.
The support Rep wasn't entirely sure how I did it until he saw me do it through a screen sharing tool. One thing we discovered over the phone and through screen sharing is that this only happens when using the built-in trackpad or the Magic Trackpad. This doesn't occur when using a mouse. That I did not know until the Apple Support rep tried to replicate it on his Mac, but couldn't because he was using a Mouse but was able to 100% replicate when using the trackpad. Then we checked my trackpad settings and all was fine (he thought maybe it had to do with the 3-finger drag...which I have turned off by default). I asked him to reproduce it on his Mac, and he was finally able to do it 100% of the time. So we were able to rule out several things to pinpoint it. First, it's not an issue with my Mac (Late 2012 MBP, 2.9 i7 w/ 750GB HDD), since his (newer) Mac could reproduce it (as well as my friend's Mac which is 4 years older than mine, same MBP but late 2008). Second, it's definitely a "bug" because we could 100% reproduce it and it doesn't happen in any other Mac stock app or any 3rd part app). He was very hesitant to call it an official "bug" but conceded because we could consistently reproduce the exact same method. Third, it only happens when using a trackpad. So, it could be one of 2 things, a bug in Messages or a bug in the trackpad coding. We are assuming the former because it doesn't happen in any other app.
So, after the Support Rep tried to contact a Senior Support member to discuss filing a bug (and not being able to get one right away), he told me he will file the bug for me and after that there is no way for him to notify me if the report has been seen or responded too by the Apple Dev team. So he said i'll have to just wait and check the OS X update descriptions to see if the bug has been addressed...and to "tell all my friends that I found reported it 'first' to Apple". Which i thought was funny that he mentioned that. Sounds like, besides this forum, nobody at Apple Support has heard of this issue being reported...or at least according to this Support Rep I spoke with.
So, hopefully we'll see this issue resolved in one of the next updates...let's hope before 10.11 comes out. It's such a minor (but annoying) thing, that I really doubt it will be much of a priority though.