[deviceorientation] Behavior when event data cannot be provided is underspecified (#118)

rakuco has just created a new issue for https://github.com/w3c/deviceorientation:

== Behavior when event data cannot be provided is underspecified ==
Each of the 3 event types defined in this specification have an excerpt that looks like this:

> If an implementation can never provide motion information, the event should be fired with the acceleration, accelerationIncludingGravity and rotationRate attributes set to null.

This does not look entirely clear to me:
- Should implementations fire a single event with nullable attributes set to null, or does the text intend to give implementations some leeway so that they can continue trying (and consequently fire any number of "empty" events)?
- Doesn't it make more sense to just not fire an event at all?

Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/118 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 10 November 2023 15:24:52 UTC