-
Bug
-
Resolution: Fixed
-
P3
-
8
-
b06
-
x86
-
linux
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8045646 | 8u25 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8040206 | 8u20 | Sergey Bylokhov | P3 | Resolved | Fixed | b11 |
| JDK-8053874 | emb-8u26 | Sergey Bylokhov | P3 | Resolved | Fixed | b17 |
| JDK-8264496 | 7u311 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8259365 | 7u301 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
| JDK-8260038 | 7u291 | Sergey Bylokhov | P3 | Closed | Fixed | b32 |
The general bug is that we repaint native part of the XComponentPeer after UPDATE event.
Small testcase attached. If you see the cross in the window the test passed otherwise failed.
Note that test works on MToolkit and WToolkit.
The same bug was fixed on macosx:7125657.
Because of this issue our incremental paint functionality does not work.
- backported by
-
JDK-8040206 XAWT: Native components should not paint native part on UPDATE event
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
-
- Closed
-