W3C home > Mailing lists > Public > public-device-apis-log@w3.org > May 2017

Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 May 2017 10:10:26 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304625580-1496052625-sysbot+gh@w3.org>
I'm kind of confused why we would move back to **option 1** after having had consensus to move to **option 2** or **option 3**.

I initially spec'ed **option 1** because my understanding was that it was (a) what was implemented in both Android and iOS and thus something developers would be used to (according to you, that's not the case), and (b) it would be a lot simpler and less resource hungry to implement.

> The only good option would be having 1-to-1 mapping between Sensor object and platform sensor.

I'm no longer sure about that actually. It becomes especially complicated if we need both rAF-sync and non-rAF sync on the same page.

Decoupling the sensor object from sensor observers is something I suggested in the past already and that could make sense looking into again, but I don't think we'd be able to move to a singleton altogether.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/152#issuecomment-304625580 using your GitHub account
Received on Monday, 29 May 2017 10:10:32 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:54 UTC