W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Screen Orientation Status

From: Bruno Racineux <bruno@hexanet.net>
Date: Mon, 07 Apr 2014 16:08:58 -0700
To: Mounir Lamouri <mounir@lamouri.fr>, <public-webapps@w3.org>
Message-ID: <CF6457AC.85BF0%bruno@hexanet.net>
On https://www.w3.org/Bugs/Public/show_bug.cgi?id=25088 :

You cannot fire on window without also having the window.orientation
property (with its own issues*). That would break existing code relying on
the webkit api (expecting to read a value on window.orientation).

I am not sure, I was able to get my point across previously, for lack of
feedback on it, but I strongly believe that mixing 'device' orientation
and 'screen' orientation is a mistake going forward and important point.

In the not so distant future, we will likely use screens 'attached'
to mobile devices. In that, the screen will be entirely independent from
the mobile table/phone/watch/etc.

Sample use case:
Let's imagine an ipad like 'iScreen' plugged to an iPad with dual screen
capability with two different browser viewport on each screen.  When the
iPad rotates, it shall only fire for the iPad screen, not the external
iScreen if the later doesn't rotate, and vice-versa.

How will you differentiate those two from an implementation standpoint?
I have no idea how that goes, but I'd like to raise that question.

*In that case, the window events would not, and shall not be expected, to
fire at the same time. IMO, one component here *must* remain 'mobile
device/embedded screen' based. And the other purely screen (either
external or embedded). Or I think there will be implementation hurdles or
confusion
down the road.

Unless I am mistaken, the webkit window.orientation API speaks of 'device'
as purely of an 'embedded screen device'. Accordingly, I think we should
clearly dissociate 'device' from 'screen', or it may narrow and limit the
scope of usage. I don't think that a unique API without the above
distinctions is the appropriate forward compatible way to go.

If Screen Orientation must fire at the window level, perhaps let's use a
different name such as window.screenorientationchange.


-Bruno


On 4/3/14 2:36 PM, "Mounir Lamouri" <mounir@lamouri.fr> wrote:

>Hi,
>
>I have just updated the specification WD, solving most of the
>outstanding issues:
>https://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html (it
>is hot off the press, be gentle with typos and nits)
>
>There are now only two outstanding bugs now:
>https://www.w3.org/Bugs/Public/show_bug.cgi?id=25053
>https://www.w3.org/Bugs/Public/show_bug.cgi?id=25054
>
>I have an idea on how to handle them but I would like to discuss those
>during the F2F next week.
>
>Implementation status:
>- Implemented and shipped prefixed in Firefox Desktop, Firefox Mobile
>and Firefox OS;
>- Implemented and shipped prefixed in IE11 Mobile;
>- Currently being implemented in Blink for Chrome Android
>(implementation match current ED).
>
>Note: the implementations are not compatible with the current ED but no
>implementer raised concerns about the changes when discussed here.
>
>Path to LC:
>Unless there are new outstanding issues being raised, I would like to go
>to LC when the two bugs above are fixed. Hopefully just after the F2F.
>
>Test suite:
>None yet. No test suite coordinator at the moment.
>
>Thanks,
>-- Mounir
Received on Monday, 7 April 2014 23:09:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:23 UTC