-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b09
-
x86, sparc
-
linux, solaris
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2146417 | 6u1 | Yuri Nesterenko | P2 | Resolved | Fixed | b05 |
Since fix to 4360364 in JDK 6.0, XAWT, pressing of Ctrl+ascii letter stopped to produce unicode control characters like Ctrl+a --> 0x01 etc. Instead, under XAWT, we receive KEY_TYPED with Unicode of the pressed ascii character and modifier Ctrl.
For certain applications it may be better to receive such pair because it could resolve ambiguity like one in 6494868. However older releases of JDK on all platforms fire KEY_TYPED with control characters, so we should treat this change as regression.
For certain applications it may be better to receive such pair because it could resolve ambiguity like one in 6494868. However older releases of JDK on all platforms fire KEY_TYPED with control characters, so we should treat this change as regression.
- backported by
-
JDK-2146417 Since JDK 6.0 in XAWT, Ctrl+ascii letter results in KEY_TYPED ascii letter, not control char
-
- Resolved
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-