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

Re: [sensors] Define processing model

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Fri, 26 May 2017 14:44:50 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304301705-1495809889-sysbot+gh@w3.org>

> Event handler invocation is required regardless of design.

Well, it's really not necessary for rAF sync'ed stuff, which instead is just going to get the values from the sensor attributes on each new frame.

One rational proposal could have been to only allow rAF-synced sensors in the main window (maybe even without events?), and forced all other non-rAF sensor uses into workers.

>> Especially if complex filtering is done on them.
> We don't have filtering on renderer side, if we would have any, it would be outside of the process that renders page.

I was referring to filtering happening in JS.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/198#issuecomment-304301705 using your GitHub account
Received on Friday, 26 May 2017 14:44:57 UTC

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