This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24703 - No easy way to lock to a set of accepted orientations if one UA doesnt support one of them
Summary: No easy way to lock to a set of accepted orientations if one UA doesnt suppor...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Screen Orientation (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Mounir Lamouri
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 18:48 UTC by Kenneth Rohde Christiansen
Modified: 2014-03-14 20:23 UTC (History)
2 users (show)

See Also:


Attachments

Description Kenneth Rohde Christiansen 2014-02-17 18:48:25 UTC
Some apps and games might work fine in a set of orientation and thus try to lock to the accepted set or orientations. That might be [portrait-primary, portrait-secondary], unfortunate that lock will fail for UAs disabling portrait-secondary due to:

For each orientation in the orientations list, run the following sub steps:
If orientation isn't part of the allowed orientations, the steps must stop here and return false.

Which means that the app will have to try to relock to any kind of subset of the decided allowed orientations.
Comment 1 Kenneth Rohde Christiansen 2014-02-17 18:53:10 UTC
A way to get around it is allowing allowed orientations in the below to differ per UA. Ie one UA might have portrait mean just portrait-primary.

"If orientation is portrait or landscape the value must be removed from orientations and every allowed orientations it is representing must be inserted in orientations."

If we go down that road we might want to add "any" meaning any allowed portrait and landscape orientation