{ "id": "62380", "key": "TIMOB-1748", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2017-05-26T17:31:14.000+0000", "created": "2011-04-15T03:01:15.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "android", "focus", "trackball" ], "versions": [], "issuelinks": [], "assignee": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-05-26T17:32:03.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "{html}

The following test cases require the user to tap the screen\nbefore the focus rect appears by way of the trackball. In some\ncases, if I use a tap to get to the test, the track ball works, but\nif I use the trackball to to make the selection, the resulting test\nwil not show the focus rect.

\n

so,
\ntrackball to make selection in list>trackball fails in test
\nfinger tap in list>trackball works. That make any sense? :-P

\n

Base UI>tab groups
\nBase UI>window Properties
\nBase UI>window layout
\nBase UI>window (Stand Alone) (all generated windows from this\ntest)
\nBase UI>Custom Events
\nBase UI>View>scroll view>scrollable view (unable to focus\non ui on bottom)
\nBase UI>Views>Table>Update rows
\nBase UI>views>options dialog

\n

controls>slider
\ncontrols >button

\n

Phone>sound

{html}", "attachment": [], "flagged": false, "summary": "Android : list of KS cases in which trackball does not give focus to onscreen elements", "creator": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "126540", "author": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

(from [5949bc7265e449dd0ae6e62b4b95b5ba77177f1c])\n[#1748 state:fixed-in-qa] Code cleanup to not\nrequest getLayout() more than once. Fixed trackball focus. Since\nAndroid has the concept of touchable focus, your action on a\npreceding window in KS has an effect on the next window. For\nexample, if you touch select a test, trackball focus will work on\nthe next window. This seemed to be working before. If you\ntrackball/dpad select, then it failed to let you use the\ntrackball/dpad on the next activity. After the fix you should\nnotice distinct behaviors. If you touch select and go to the next\ntest, you will not see a focused item in most cases. If you\ntrackball/dpad select then you will see a control with focus on the\nnext Activity. \nhttp://github.com/appcelerator/titanium_mobile/commit/5949bc7265e44...

{html}", "updateAuthor": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T03:01:16.000+0000", "updated": "2011-04-15T03:01:16.000+0000" }, { "id": "126541", "author": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

These still fail (in that trackball does not give focus, wether\nits touch or trackball that invokes the window):

\n

Base UI> window (Stand Alone)> Open (plain)
\nBase UI> window (Stand Alone)>Open (Nav Bar COvered)
\nBase UI> window (Stand Alone)>Open (Fullscreen)

{html}", "updateAuthor": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T03:01:16.000+0000", "updated": "2011-04-15T03:01:16.000+0000" }, { "id": "133621", "author": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "body": "closing to open", "updateAuthor": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-05-15T12:35:01.000+0000", "updated": "2011-05-15T12:35:01.000+0000" }, { "id": "133622", "author": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "body": "issue noted in the comments persists. Was \"open\" \"fixed in qe\", closed and reopened so Don will see. Happy to punt to 1.8.0", "updateAuthor": { "name": "thomashuelbert", "key": "thomashuelbert", "displayName": "Thomas Huelbert", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-05-15T12:35:45.000+0000", "updated": "2011-05-15T12:35:45.000+0000" }, { "id": "420529", "author": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket as Invalid as this version of Kitchen Sink is no longer supported.", "updateAuthor": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2017-05-26T17:31:14.000+0000", "updated": "2017-05-26T17:31:14.000+0000" } ], "maxResults": 5, "total": 5, "startAt": 0 } } }