I had some other thoughts about this function as well.  E.g. should it really force the click to be on the visible area of the viewer?  E.g. if you to test some of the visibility constraints, you might want to simulate a click outside of the bounds.

I put the equivalent navigator click and drag operations in the navigator code. I found it worked better for my test cases to have the parameters in terms of pixels rather than points.  I had them in util.js at one point, but I moved them out because I thought it was strange to have the two sets of functions alongside each other with similar concepts but different behaviors (pixel vs points, and force onto viewer region vs not)  I also wasn't sure if there was really a need for navigator click operations in any of the other tests.  However, that said, I can stil see the argument for moving the navigator click and drag functions back into util.js if folks think that would be better.