{ "id": "63134", "key": "TIMOB-2502", "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": "2", "description": "The problem described is an issue which will never be fixed.", "name": "Won't Fix" }, "resolutiondate": "2013-08-01T00:33:24.000+0000", "created": "2011-04-15T03:21:24.000+0000", "priority": { "name": "Trivial", "id": "5" }, "labels": [ "android", "font", "ios", "jss", "klist", "rplist" ], "versions": [], "issuelinks": [], "assignee": { "name": "blainhamon", "key": "blainhamon", "displayName": "Blain Hamon", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-20T17:53:51.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 JSS parser seems to have issues when it encounters curly\nbraces:
\n\nfont:{fontSize:15, fontWeight:'bold'};\n\nshadowOffset:{x:0, y:1};
\n
\nThe first line can be rewritten in JSS using CSS syntax as\nfollows:
\n\nfont-size:15;\nfont-weight:'bold';
\n
\nThis seems to be magically understood by Titanium.
\nBut the CSS equivalent for shadows does not work:
\n\ntext-shadow: 0 1 #6E7983;
\n
\nThe parser also requires JSS properties to be separated by\nsemi-colons and not by commas, which means properties can't simply\nbe cut and pasted from code files into JSS files. Not sure if this\nis by design, but it's a bit of a hassle.
Maybe also affects android?
I just verified that this also does not work on Android, and I\ncollected some relevant logs.
\nIf necessary, I can split off an Android ticket.
\nBROKEN on Android Device Samsung Epic 4G running Android 2.2
\nBROKEN on iPhone Simulator 4.3
\nBROKEN with Titanium Mobile 1.6.2 (03/30/11 17:25 0243d42...)
\nBROKEN with Titanium Mobile 1.7.0 (04/05/11 10:30 731db9c...)
Regardless of the platform, the following syntax errors show up\nin the build logs:
\n\nSyntax error at 'LexToken(LBRACE,' {',1,106)'\nSyntax error at 'LexToken(S,' ',1,111)'\nSyntax error at 'LexToken(S,' ',1,117)'
\n
\nOn Android, these errors show up right after \"[INFO] Copying\nplatform-specific files ...\" and on iOS right after \"[INFO] iPhone\nsimulated device: iphone\".
\n