- 
    Bug 
- 
    Resolution: Fixed
- 
     P3 P3
- 
    6, 7, 8
- 
        b06
- 
        generic
- 
        linux_ubuntu, windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8045488 | 8u25 | Unassigned | P3 | Resolved | Fixed | b01 | 
| JDK-8033226 | 8u20 | Oleg Pekhovskiy | P3 | Resolved | Fixed | b01 | 
| JDK-8053728 | emb-8u26 | Unassigned | P3 | Resolved | Fixed | b17 | 
If displays are duplicated, test passes. But if displays are extended, test fails.
To reproduce use attached test.
- backported by
- 
                    JDK-8033226 Robot moves mouse to point which differs from set in mouseMove on Unity shell -           
- Resolved
 
-         
- 
                    JDK-8045488 Robot moves mouse to point which differs from set in mouseMove on Unity shell -           
- Resolved
 
-         
- 
                    JDK-8053728 Robot moves mouse to point which differs from set in mouseMove on Unity shell -           
- Resolved
 
-         
- duplicates
- 
                    JDK-4821707 Win32:Robot should not save an offset when created with a non-default GraphicsDe -           
- Closed
 
-         
- relates to
- 
                    JDK-8017567 [macosx] MouseInfo.getPointerInfo() may be null after robot.mouseMove(x,y) if x,y is on secondary screen -           
- Open
 
-         
- 
                    JDK-8155744 [TEST_BUG] robot.mouseMove again broken on Unity dual-screen -           
- Open
 
-         
- 
                    JDK-8033128 Javadoc change is required for java.awt.Robot(GraphicsDevice screen) constructor -           
- Resolved
 
-         
- 
                    JDK-6287244 Linux/Solaris robot should be rewritten -           
- Resolved
 
-         
- 
                    JDK-8014212 Robot captures black screen -           
- Resolved
 
-