{ "id": "63312", "key": "TIMOB-2680", "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": [ { "id": "11244", "name": "Release 1.7.0", "archived": true, "released": true, "releaseDate": "2011-06-13" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-05-17T15:09:06.000+0000", "created": "2011-04-15T03:26:49.000+0000", "priority": { "name": "Trivial", "id": "5" }, "labels": [ "2.3", "android", "defect", "hinttext", "keyboard", "reported-1.5.1" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-05-17T15:09:06.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}
1.5.1 + hvga skinned 2.3 emulator. Not seen in 2.2
\n1.Base UI > views > scroll views > scroll views text\narea
\n2.click into a text field
\n3.note the keyboard and hint text behavior
results:keyboard pops up,. hint text appears and the content\nthen dissapear, but leave the hint text bar up.
\nexpected: populated hint bar or no hint bar?
screen shot
\nhttps://skitch.com/thomashue/rg28f/5560-titanium-15-hvga
Seeing a lot of these UI discrepancies in the 2.3 emulator, it\nseems to be buggy in general. This looks great on Nexus S -- my\nguess is Google has quite a few known UI bugs in the current\nversion of the emulator. Thomas, kicking back to you for\nverification that it works on device.. not sure what else we can do\nwith core tooling problems like this.