{ "id": "61011", "key": "TIMOB-379", "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": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-07-26T18:48:48.000+0000", "created": "2011-04-15T02:28:20.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "feature", "ios", "iphone", "searchbar" ], "versions": [], "issuelinks": [], "assignee": { "name": "rseagraves", "key": "rseagraves", "displayName": "Reggie Seagraves", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-07-26T18:48:48.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": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
Enhancement suggestion: Currently, when cancel is 'true', the\ncancel button is always displayed. It's disabled if the search\ninput doesn't have the focus.
\nI believe that a different behavior would create a cleaner UI:\nMake the cancel button invisible instead of disabled when the\nsearch bar doesn't have the focus. On the iPhone platform, the\ndisabled state is still somewhat 'active'-looking. The presence of\nthe disabled button is also unnecessary clutter.
This is very easy to implement - see the new\nsetShowCancel
method in \nthis thread.
This has my vote; I'm currently having to programmatically do\nit.