-
Type:
Bug
-
Resolution: Not an Issue
-
Priority:
P2
-
Affects Version/s: 1.4.2, 6
-
Component/s: client-libs
-
x86
-
windows_vista
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2196236 | 6-pool | Unassigned | P3 | Closed | Not an Issue | |
| JDK-2196235 | 5.0-pool | Unassigned | P5 | Closed | Won't Fix | |
| JDK-2196234 | 1.4-pool | Unassigned | P5 | Closed | Won't Fix |
Java application, executed from inactive console, stays inactive under Windows Vista.
Moreover, executing toFront() has no effect.
Executing:
isActive() -> true
isFocusable() -> true
isFocused() -> true
isShowing() -> true
executing same commands when window is inactive under linux gives an output:
isActive() -> false
isFocusable() -> true
isFocused() -> false
isShowing() -> true
This issue has critical impact to our testing automation under Windows Vista.
Moreover, executing toFront() has no effect.
Executing:
isActive() -> true
isFocusable() -> true
isFocused() -> true
isShowing() -> true
executing same commands when window is inactive under linux gives an output:
isActive() -> false
isFocusable() -> true
isFocused() -> false
isShowing() -> true
This issue has critical impact to our testing automation under Windows Vista.
- backported by
-
JDK-2196236 java application, executed from inactive console, can't be maden active programaticly
-
- Closed
-
-
JDK-2196234 java application, executed from inactive console, can't be maden active programaticly
-
- Closed
-
-
JDK-2196235 java application, executed from inactive console, can't be maden active programaticly
-
- Closed
-