- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Aug 2018 10:41:10 +0000
- To: public-geolocation@w3.org
Generic Sensor API defines a [local coordinate system](https://w3c.github.io/sensors/#local-coordinate-system) that can be either the [device coordinate system](https://w3c.github.io/accelerometer/#device-coordinate-system) or the [screen coordinate system](https://w3c.github.io/accelerometer/#screen-coordinate-system). The Accelerometer, Gyroscope, and Magnetometer specifications that decompose the `DeviceOrientationEvent` and `DeviceMotionEvent` into low-level primitives as well as the fusion sensor Orientation Sensor use these concepts, and allow the web developer to define whether the local coordinate system is to be bound to the device coordinate system or the screen coordinate system addressing this issue. https://w3c.github.io/accelerometer/#enumdef-accelerometerlocalcoordinatesystem https://w3c.github.io/gyroscope/#enumdef-gyroscopelocalcoordinatesystem https://w3c.github.io/magnetometer/#enumdef-magnetometerlocalcoordinatesystem https://w3c.github.io/orientation-sensor/#enumdef-orientationsensorlocalcoordinatesystem **Proposal**: Since the Generic Sensor-based APIs now provide a modern API surface that satisfies this requirement, close this PR and do not add this new feature to the DeviceOrientation Event spec. Any concerns, please let us know in the PR comments. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/pull/10#issuecomment-414273500 using your GitHub account
Received on Monday, 20 August 2018 10:41:12 UTC