The Robot functionality on windows only works on the primary display. If
the user wants to perform operations on the seconday display, they won't
necessarrily get what they wanted. For example, the palette information
used only takes the primary screen into account.

I don't have a specific example of the failure; the bug report comes from
reading the code in awt_Robot.