{ "id": "61694", "key": "TIMOB-1062", "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": "11224", "name": "Release 1.4.0", "archived": true, "released": true, "releaseDate": "2010-07-16" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T02:42:58.000+0000", "created": "2011-04-15T02:42:56.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "android", "button", "defect", "enabled", "ios", "iphone" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-02T19:21:38.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}
A button that has enabled set to false still fires events.
\nvar test_btn = Ti.UI.createButton({
\ntitle:'test',\nwidth:100,\nheight:35,\ntop:0,\nleft:0,\nenabled:false
\n
\n});
\ntest_btn.addEventListener('click',function(e){
\nTi.API.log('am I firing?');
\n
\n});
\nwin.add(test_btn);
Disabling buttons works correctly, but Blain says there may be\ntoolbar strangeness. Investigating.
Is this working correctly in the version in HEAD? Because I can\nrecreate this bug in 1.2 & 1.3
It works for me off master/HEAD, yes.
(from [24118fb786421474ee3d0a518ef033dea44f527a])\n[#1062 state:invalid] Test for disabled button in\ntoolbar. Works as expected. \nhttp://github.com/appcelerator/titanium_mobile/commit/24118fb786421...
Re-open if you can duplicate under master/HEAD, and I've somehow\nmissed something.
Disabling a button works on iPhone but is definitely broken on\nAndroid. In the latest KitchenSink, go to\n/Resources/examples/button.js. Comment out lines 55-59, the\nsetTimeout function. On iPhone you can click the button once to\ndisable it, and once disabled, it no longer responds to events. On\nAndroid, click it once to \"disable\" it, but you can continue to\nclick it and it will respond to the click events.
\nCan this bug be reopened or should a new one be filed?