W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2017

Re: Discussion: Change to SC 2.6.2 Orientation

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Wed, 18 Oct 2017 16:30:09 +0100
To: w3c-wai-gl@w3.org
Message-ID: <6fc65c08-4e44-77a8-0a29-a60ffb6645cc@splintered.co.uk>
On 18/10/2017 16:25, White, Jason J wrote:
>> -----Original Message-----
>> From: Patrick H. Lauke [mailto:redux@splintered.co.uk]
>> Maybe I'm misunderstanding, or this is splitting terminology, but If there's a
>> mechanism to change it, then it's not locked, surely?
> [Jason] According to the terminology used in the screen orientation API, even if there's a mechanism to change it, the orientation is locked. The example is that given in the GitHub issue: a button that calls the lock() method to lock the orientation when the user presses it.
> https://www.w3.org/TR/screen-orientation/

But it's not locked irreversibly. The user can still unlock it, no? It's 
an active choice the user can take.

So does the language need to explicitly say something along the lines of 
"Don't lock the content orientation, unless a mechanism is available for 
the user to unlock it or to explicitly set/change orientation, or if a 
particular orientation is essential..." ?

Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 18 October 2017 15:30:33 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:18 UTC