Re: [sensors] Should the enum SensorState have nosensor ?

We're converging on:

1. dropping usage of promise for `start()` and `stop()` methods,
2. removing the `onstatechange` event handler,
3. turning the `SensorState` enum into slots (or similar unexposed 
thingies),
4. renaming the "active" state into "activated",
5. adding an `onactivate` handler which is called when the state 
transitions from "activating" to "activated".

```webidl
interface Sensor : EventTarget {
  readonly attribute SensorReading? reading;
  void start();
  void stop();
  attribute EventHandler onchange;
  attribute EventHandler onactivate;
  attribute EventHandler onerror;
};
```

Code examples to follow.

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/104#issuecomment-248316955 using
 your GitHub account

Received on Tuesday, 20 September 2016 14:25:39 UTC