Comment 2 for bug 971926

Revision history for this message
Joanmarie (joanmarie-diggs-deactivatedaccount) wrote :

As you will see in the attached log file (created by using the previously-attached tester and performing the steps in the opening report):

1. Up and Down initially result in accessible events:

>>> KEY PRESSED: Up
<<< KEY RELEASED: Up
object:state-changed:focused(1, 0, 0)
 source: [password text | Enter password for Joanmarie Diggs]
 host_application: [application | unity-greeter]
>>> KEY PRESSED: Down
<<< KEY RELEASED: Down
object:state-changed:focused(1, 0, 0)
 source: [push button | Login as Guest Session]
 host_application: [application | unity-greeter]
>>> KEY PRESSED: Up
<<< KEY RELEASED: Up
object:state-changed:focused(1, 0, 0)
 source: [password text | Enter password for Joanmarie Diggs]
 host_application: [application | unity-greeter]

2. But after arrowing within the menu that results from pressing F10 and then pressing Escape, events go AWOL:

>>> KEY PRESSED: Escape
object:state-changed:iconified(0, 0, 0)
 source: [window | ]
 host_application: [application | unity-greeter]
window:deactivate(0, 0, Login Screen)
 source: [frame | Login Screen]
 host_application: [application | unity-greeter]
<<< KEY RELEASED: Escape
>>> KEY PRESSED: Down
<<< KEY RELEASED: Down
>>> KEY PRESSED: Up
<<< KEY RELEASED: Up
>>> KEY PRESSED: Down
<<< KEY RELEASED: Down
>>> KEY PRESSED: Up
<<< KEY RELEASED: Up
>>> KEY PRESSED: Down
<<< KEY RELEASED: Down
>>> KEY PRESSED: Up
<<< KEY RELEASED: Up
>>> KEY PRESSED: Up
<<< KEY RELEASED: Up
>>> KEY PRESSED: Down
<<< KEY RELEASED: Down