I agree with Kevin here. The outcome of the sequence in bug description is quite unpredictable from the user point of view. In the step 6 I could imagine user for example answering a phone call and keeping the phone in portrait orientation for a while. And then finally when switching to browser on a flat-down phone it suddenly orientates to portrait. And what is worse for the user is that the whole shell and therefore right edge switcher changes place making the whole system navigation more difficult.
But I also understand that technical complexity aspect here as well. If I could decide I guess I would ignore orientation switches when fixed- orientation app is focused and ask the orientation again when rotation- enabled app is focused. And if the sensors are between the threshold values "Don't change" status should be given instead of the last remembered orientation. Does this all make sense? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1500633 Title: orientation sensor "last vertical" seems to be remembered and applied Status in QtMir: Incomplete Status in Ubuntu UX: Triaged Status in qtmir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: latest rc-image 1. download and install machines vs machines 2. open machines vs machines 3. open browser, rotate to landscape 4. lay flat on table so that browser is still in landscape 5. switch back to machines vs machines with launcher 6. raise top of phone as to make the phone vertical in portrait, lay back down flat 7. switch to browser expected: browser would be in landscape actual: browser rotates To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1500633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
