{
	"id": "175003",
	"key": "TIMOB-27893",
	"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": null,
		"resolutiondate": null,
		"created": "2020-05-08T19:10:35.000+0000",
		"priority": {
			"name": "None",
			"id": "6"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": null,
		"updated": "2020-06-22T19:59:20.000+0000",
		"status": {
			"description": "The issue is open and ready for the assignee to start work on it.",
			"name": "Open",
			"id": "1",
			"statusCategory": {
				"id": 2,
				"key": "new",
				"colorName": "blue-gray",
				"name": "To Do"
			}
		},
		"components": [
			{
				"id": "10202",
				"name": "Android",
				"description": "Android Platform"
			}
		],
		"description": "On Android, setting views to {{myView.opacity = 0.0}} still triggers the touch events of the view(s) that are hidden. This does not happen for iOS and is a parity issue on Android as views that are hidden should really be hidden completely. ",
		"attachment": [],
		"flagged": false,
		"summary": "Android: Setting views to \"opacity: 0.0\" does still trigger touch events (parity)",
		"creator": {
			"name": "hknoechel",
			"key": "hansknoechel",
			"displayName": "Hans Knöchel",
			"active": true,
			"timeZone": "Europe/Berlin"
		},
		"subtasks": [],
		"reporter": {
			"name": "hknoechel",
			"key": "hansknoechel",
			"displayName": "Hans Knöchel",
			"active": true,
			"timeZone": "Europe/Berlin"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "455409",
					"author": {
						"name": "michael",
						"key": "michael",
						"displayName": "Michael Gangolf",
						"active": true,
						"timeZone": "Europe/Berlin"
					},
					"updateAuthor": {
						"name": "michael",
						"key": "michael",
						"displayName": "Michael Gangolf",
						"active": true,
						"timeZone": "Europe/Berlin"
					},
					"created": "2020-05-08T19:46:07.000+0000",
					"updated": "2020-05-08T19:46:07.000+0000"
				},
				{
					"id": "455412",
					"author": {
						"name": "michael",
						"key": "michael",
						"displayName": "Michael Gangolf",
						"active": true,
						"timeZone": "Europe/Berlin"
					},
					"body": "Possible PR: https://github.com/appcelerator/titanium_mobile/pull/11695\r\n\r\nonly the visible view is returning touch events.\r\nInvisible OR touchEnabled(false) view never returns touch events.\r\n\r\nThere might be an easier solution but it works :)",
					"updateAuthor": {
						"name": "michael",
						"key": "michael",
						"displayName": "Michael Gangolf",
						"active": true,
						"timeZone": "Europe/Berlin"
					},
					"created": "2020-05-08T20:43:34.000+0000",
					"updated": "2020-05-08T20:43:34.000+0000"
				},
				{
					"id": "455901",
					"author": {
						"name": "jquick",
						"key": "jquick",
						"displayName": "Joshua Quick",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "There is actually a practical use-case for having a transparent view to steal touch events.\r\n\r\nI've done this when creating my own custom dialogs (and overlays too). When doing this, you actually want an invisible view to fully fill the screen to steal touches around the dialog. That way, touching outside the dialog can be used to either dismiss the dialog or do nothing to force the end-user to make a selection.\r\n\r\nI think the way Android is doing it is correct. I know Windows Phone worked this way too (I've implemented a custom dialog as described above). If you don't want the invisible view to accept touches, then it's \"touchEnabled\" property should be set {{false}}.",
					"updateAuthor": {
						"name": "jquick",
						"key": "jquick",
						"displayName": "Joshua Quick",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2020-06-20T03:28:48.000+0000",
					"updated": "2020-06-20T03:28:48.000+0000"
				},
				{
					"id": "455904",
					"author": {
						"name": "michael",
						"key": "michael",
						"displayName": "Michael Gangolf",
						"active": true,
						"timeZone": "Europe/Berlin"
					},
					"updateAuthor": {
						"name": "michael",
						"key": "michael",
						"displayName": "Michael Gangolf",
						"active": true,
						"timeZone": "Europe/Berlin"
					},
					"created": "2020-06-20T07:43:18.000+0000",
					"updated": "2020-06-20T07:43:18.000+0000"
				},
				{
					"id": "455910",
					"author": {
						"name": "jquick",
						"key": "jquick",
						"displayName": "Joshua Quick",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Yes, [TIMOB-26581] needs to be solved. I agree. If resolving that ticket will solve the issue for you, then I'd rather we tackle that ticket.",
					"updateAuthor": {
						"name": "jquick",
						"key": "jquick",
						"displayName": "Joshua Quick",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2020-06-22T19:59:20.000+0000",
					"updated": "2020-06-22T19:59:20.000+0000"
				}
			],
			"maxResults": 5,
			"total": 5,
			"startAt": 0
		}
	}
}