This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Jul/0166.html Kornel suggests: """ Since specific, locked screen orientation is mostly needed in games, and forced rotation is disruptive to other things on the screen (e.g. moving buttons/addressbar to other physical edge of the screen), maybe it should be tied to the Fullscreen API? element.requestFullscreen({orientation:'landscape', autorotation:false}) """ Seems compelling. What do people think?
I have been suggesting this long ago, so I am positive. I thought this was a better solution that the screen orientation lock currently found in Firefox OS, as it also allows to animation the transition (potentially a scale and rotate, like opening a landscape video in portrait mode Safari).
I think this makes a lot of sense - however, it most probably needs to be possible to be a bit more specific regarding the orientation request to have full control over interaction between orientation lock, orientation events and device motion. A few links to read as background: Differences between implementations: http://mobiforge.com/developing/story/html5-mobile-web-device-orientation-events Some comments I made a long time ago: http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0063.html In general, it would be VERY beneficial for both spec'ers, browser engine implementers and webapps developers if specs like THIS would be done in collaboration between the three groups. There is a big room for failure here (as we have seen with a recent rush of specs from an org that needed to get things in fast for some device) - but also great potential to change the balance of native vs pure web games (and apps) if done right.
See also this e-mail from Tobie: http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Sep/0095.html
(In reply to Anne from comment #0) > In > http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Jul/0166.html > Kornel suggests: > > """ > Since specific, locked screen orientation is mostly needed in games, and > forced rotation is disruptive to other things on the screen (e.g. moving > buttons/addressbar to other physical edge of the screen), maybe it should > be tied to the Fullscreen API? > > element.requestFullscreen({orientation:'landscape', > autorotation:false}) > """ > > Seems compelling. What do people think? Sounds a bit early to add the orientation information to the Fullscreen API. If the UX of going fullscreen then changing orientation is terrible, we should probably introduce such a thing but so far I am not sure we got such feedback.
Mounir, this is resolved now, correct?
(In reply to Anne from comment #5) > Mounir, this is resolved now, correct? How so? Screen Orientation defines how the Fullscreen API and the Screen Orientation API are related - which is up to the UA. The Fullscreen specification doesn't define how to lock the orientation when going fullscreen. Which is for the best I believe. Is that a reasonable "FIXED" state to you?
Reasonable WORKSFORME.