-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 1.0.2fcs
-
Component/s: client-libs
-
None
-
1.0.3
-
x86
-
generic
Currently adding PropertyChangeListeners to accessible objects of a newly opened window is done asynchronously in the EventQueueMonitor class. This bears the risk that at the time the initiallly focussed component processes its FOCUS_GAINED event, there is not yet a listener attached to its AccessibleContext, so the ACCESSIBLE_STATE_PROPERTY change event to FOCUSED will get lost.
As a result, the user won't be informed which object in a dialog has the keyboard focus until (s)he starts traveling around.
This applies to all Java applications.
As a result, the user won't be informed which object in a dialog has the keyboard focus until (s)he starts traveling around.
This applies to all Java applications.