Steps to reproduce: 1.go into the 3rd part app "Game Pack"; 2.select four games: farm lines, zombie match, magic stones, tip tap tile; Expected: 1.it shows complete in vertical; Actual: 1.it does not shows completely in vertical. It only shows a half. build ID:20130426165700 build information: gaia commit: e25b349 Merge pull request #9273 from gasolin/issue-863126 gecko commit: 6dfd179 Bug 849757 - Part 4: xpcshell tests. r=vicamo, a=tef+ gaia commit: e25b349 Merge pull request #9273 from gasolin/issue-863126 gecko commit: 6dfd179 Bug 849757 - Part 4: xpcshell tests. r=vicamo, a=tef+ AU:V1.01.00.01.019.085

Jason, why this has been unnominated. Are we tracking this in a different way? From our point of view this is pretty bad

Because tech evangelism bugs do not have the ability to set blocking-b2g. We could change that, but it will require changes into Bugzilla. Note - we traditionally do not block on issues that is out of our control, which why we probably didn't turn on the blocking flags in this component.

More specific details on how I'm able to reproduce this: 1. Launch app Observe: game list is locked to portrait orientation 2. Start the Tower Jelly game Observe: game is still locked to portrait 3. Hit the Home button in the lower right hand corner to go back to the game list Observe: game list now rotates freely, and all games will rotate freely Adding Harald, who's previously worked on rotation issues with this application. Was this behavior a known limitation?

Nevermind, I found the bug: Bug 851642

Hmm....so the app manifest isn't doing an initial orientation lock, but there's some logic going on in shared.js in the app's zip file. Code in question: if ('mozLockOrientation' in screen) { var cls = document.documentElement.className, orient = 'portrait', match; if (cls && (match = cls.match(/orient-([a-z]+)/))) { orient = match[1]; } if (!screen.mozLockOrientation(orient)) { console.warn('Could not lock screen to ' + orient); } }

Pretty much exactly the same bug as bug 851642, so duping as such.

Confirmed fixed by bug 851642.