{ "id": "63177", "key": "TIMOB-2545", "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" }, { "id": "11246", "name": "Sprint 2011-11", "archived": true, "released": true, "releaseDate": "2011-03-21" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-26T09:12:20.000+0000", "created": "2011-04-15T03:22:18.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "android", "defect", "release-1.7.0", "reported-1.5.1", "rplist" ], "versions": [], "issuelinks": [], "assignee": { "name": "dthorp", "key": "dthorp", "displayName": "Don Thorp", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-26T09:12:20.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}
On Android, the default values for the Titanium.UI.Window\nproperties “fullscreen” and “navBarHidden”\nchange based on how the other is defined or not defined. The\nobvious workaround is to explicitly set the values for them for all\nwindows.
\n\"defaults to\" means \"when not specified, renders window as if\nthe value was explicitly set to\"
\nHave not tested this on iOS.
\nI've attached my app.js and RTF document containing screen\nclips. For each of the screen clips, the values of fullscreen\nand/or navBarHidden were changed or commented out and the app\nrebuilt and installed on the emulator.
Titanium SDK version: 1.5.0 (12/09/10 01:18 43358e5)
\nAndroid 2.2 APIs.
There's not an associated helpdesk ticket, but this is coming\nfrom a premium seat.
The issue here is related to our default theme and the\ndifference between \"lightweight\" and \"heavyweight\" windows.
\nFirst, regarding the default theme (which we see with the splash\nscreen). Sometime between 1.4.2 and 1.5.0 our default theme changed\nto fullscreen because of this commit:
\n\nhttps://github.com/appcelerator/titanium_mobile/commit/13242dc43342...
\nThe commit does not reference a Lighthouse ticket, so I don't\nknow why it was done.
\nNow, regarding light v heavy:
\nWhen opening a window from app.js, the window will inherit our\ndefault theme (which is now fullscreen, as evidenced above) unless\nyou specify at least one of the following properties: fullscreen,\nnavBarHidden, modal or windowSoftInputMode. If you specify any one\n(or more) of those properties when creating the window, the window\ngets its own Android Activity, which defaults to Android's default\ntheme, which is not fullscreen. If you do\nnot specify any one of those properties, the\nwindow is drawn on the existing Android Activity, which is the same\nactivity that showed the splash screen, and which is therefore\nfullscreen.
\nExamples:
\nYou specify none of those four properties in createWindow(): you\nget fullscreen, because it's using the same activity as the splash\nscreen, which is fullscreen.
\nNow specify navBarHidden (either true or false). The window will\nnot be full screen anymore because it is no longer based on our\nsplash screen theme, but rather based on the default Android theme,\nwhich is not fullscreen.
\nNot sure if we want to go back to having a non-fullscreen splash\ntheme?
@DON agreed this is not a defect? Pulled the tiapp.xml defect\n(not respecting navbar-hidden, statusbar-hidden options) into\nSprint 2011-12: #3024
Not a defect. See #3024 for the tiapp.xml problem.