You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current ondeviceorientation text has the following excerpt:
If an implementation can never provide orientation information, the event should be fired with the alpha, beta and gamma attributes set to null.
It does not say anything about the absolute attribute. This is an event without any data so its value is not relevant, but I wonder if it should be specified normatively nonetheless.
The text was updated successfully, but these errors were encountered:
We were only requiring alpha, beta, and gamma to be null. It makes sense to
also require implementations to set absolute to the same value as well.
At the time of writing, this is done for completeness' sake though:
- Blink implements this behavior and sets absolute to false when a
deviceorientation cannot be provided, and to true for
deviceorientationabsolute events.
- Gecko does not send any events if it cannot provide readings (e.g. when
there are no sensors available).
- WebKit only ships an iOS implementation, whose IDL does not even have an
absolute attribute.
Fixes#119.
We were only requiring alpha, beta, and gamma to be null. It makes sense to
also require implementations to set absolute to the same value as well.
At the time of writing, this is done for completeness' sake though:
- Blink implements this behavior and sets absolute to false when a
deviceorientation cannot be provided, and to true for
deviceorientationabsolute events.
- Gecko does not send any events if it cannot provide readings (e.g. when
there are no sensors available).
- WebKit only ships an iOS implementation, whose IDL does not even have an
absolute attribute.
Fixes#119.
The current ondeviceorientation text has the following excerpt:
It does not say anything about the
absolute
attribute. This is an event without any data so its value is not relevant, but I wonder if it should be specified normatively nonetheless.The text was updated successfully, but these errors were encountered: