Not quite the same situation but I get that error when TestComplete records a click that is negative in the y for my popup window (in this case on firefox) but on playback their click function doesn't like this negative value.
So e.g. on recording I was trying to click the maximize button which was something like (422,-19). However the Click function on playback sees that negative number (and perhaps at y = 0 as well?) as automatically invalid i.e. outside the window bounds. Also TC can't highlight the little maximize button control with the object spy which probably doesn't help. It's probably true that the minimize,maximize, close controls are technically outside the window area where all the main action happens.
I got around this at first by using the low-level recording mechanism for this one case and recording the click with screen coordinates. That worked but is a bit of a harsh workaround.
Now I have a little script function which gets the popup window object and calls the .Maximize() function to do it. Works like a charm.
But really I think this is a bug or else the result of the maximize control being unclickable. If a value is recorded on the -y for a window it should simply play it back instead of seeing it as automatically out of bounds. How else would it be recorded in the first place? They must think I was hand entering the coordinates and are trying to prevent invalid clicks from occurring.
It seems suspicious that its saying the invalid coordinate is at y = 0. Maybe any y <= 0 are invalid.
