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

Re: [sensors] Investigate adding dedicated task sources

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Tue, 30 May 2017 14:39:14 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304899293-1496155152-sysbot+gh@w3.org>
> The HTML spec leaves the task queue prioritization to implementations. I believe an implementation is most of the time in the best position to determine which task to run and when, all things considered, see https://html.spec.whatwg.org/#task-source. In normative prose https://html.spec.whatwg.org/#event-loop-processing-model this is simply:
>> The user agent may pick any task queue.

Agreed. The idea wasn't to specify prioritization here, but eventually to provide hooks in the spec(s) to make that easier, for example by using two different task source, one when latency is critical and one when it isn't.

> While we currently do not force a particular task to be of higher priority, requestIdleCallback API provides means to explicitly request a particular task to be executed only during the idle time between the frames. If used appropriately, this API will help keep jank away in use cases that involve sensors too.

That seems like an orthogonal issue.

GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/221#issuecomment-304899293 using your GitHub account
Received on Tuesday, 30 May 2017 14:39:22 UTC

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