On 10/20/15 6:12 AM, Jonas Sicking wrote:
On Tue, Oct 20, 2015 at 2:49 AM, Mounir Lamouri wrote:
Should we add this to the Screen Orientation specification?
I think so yes.
I also think so. In my mind the Compat Standard should be transitional
in nature, rather than something we maintain f
On Tue, Oct 20, 2015 at 2:49 AM, Mounir Lamouri wrote:
> Should we add this to the Screen Orientation specification?
I think so yes.
/ Jonas
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
FWIW, this is the usage of window.orientation in the wild recorded by
Chrome:
https://www.chromestatus.com/metrics/feature/timeline/popularity/285
However, Google's internal tools allow me to see the repartition between
platforms and this seen a lot by Chrome Android users.
Should we add this to
As someone pushing for the ScreenOrientation API, I agree with this
intent nonetheless.
It *might* be worth warning about this property being inconsistent,
and that it's better for users to use the ScreenOrientation API. But I
think it's really only worth doing if this is something that other
brow
*Summary*: window.orientation returns a value corresponding to the screen
orientation. The orientationchange event is fired when the orientation of
the viewport is changed. These features are non-standard but have been
implemented by other browser vendors on mobile platforms leading to
widespread u
5 matches
Mail list logo
