- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2016 20:54:37 +0000
- To: public-device-apis-log@w3.org
> I understand how you want API to behave, it is just bit confusing, maybe [Sensor.reading](https://w3c.github.io/sensors/#sensor-reading) section needs to be reformulated somehow. Heh. yeah. :) There's a lot of reformulation needed. That said, the [update current reading algorithm](https://w3c.github.io/sensors/#update-current-reading) is quite clear about this. > Spec says that [Sensor.reading](https://w3c.github.io/sensors/#sensor-reading) points to current reading. Reading is an object, therefore if I write `let cached = Sensor.reading;` by default JS engines will make reference, as a web developer I might think that cached is pointing to current reading. That's a good point in terms of meeting developer expectations. @rwaldron, WDYT? Should we use method instead, e.g.: ```js sensor.read(); ``` > While in your example, Sensor.reading getter makes a immutable clone of a current reading. That's not what happens, because if it did: `als.reading === als.reading;` would return `false` and we want it to return `true`. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/ambient-light/issues/15#issuecomment-257417774 using your GitHub account
Received on Monday, 31 October 2016 20:54:43 UTC