[Bug 25088] 'orientationchange' should fire on Window so that there can be a <body> event handler for it

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25088

--- Comment #5 from Bruno Racineux <bruno@hexanet.net> ---
(In reply to Jonas Sicking from comment #4)
> The fact that we have bugs on file doesn't mean much.

Well I only speak of Mike Taylor's expressed agreement via twitter, with the
fact that the Screen API lacks that ability to detect left and right rotations.

> We've been reluctant to add window.orientation since the API appears to be
> partially broken. It returns 0 when the device is in the "default"
> orientation. If that orientation is landscape or portrait mode is device
> specific.

I don't really understand the reluctance.

window.orientation may be broken as per initial Apple documentation of portrait
default. But it's consistent around 0 default with mobile devices. It can be
specced and understood as such in Gecko.

'landscape' or 'portrait' in relation to the viewport are not technically tied
to the device anyway. They only are if the viewport match the screen context.
So the fact that the relation between angles and window/viewport orientation is
not consistent is technically correct.

No one should expect more from window.orientation than what it currently
provides.
That is: Giving the angle relationship of the window in relation to the device
default.

> But I don't feel strongly. I don't think that being able to use <body
> onorientationchange="..."> provides that much value.

Right, and a body handler would be irrelevant to screen orientation, so those
value wouldn't necessarily match.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 20 March 2014 00:41:55 UTC