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

Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Fri, 26 May 2017 14:35:34 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304299402-1495809332-sysbot+gh@w3.org>
> Shared buffer is not exposed to JS side, it is implementation detail and internal slot.

As an internal slot, it can still have side effects on the JS side. 

> In chromium implementation there are no side-effects related to updating it during script execution, thus gyro.x === gyro.x should be true during event-handler execution.

But this is implementation specific, it is not specified by the spec, is it?

> This is fixed by #197 or by #210

I don't think it is, tbh. Maybe switching steps 6 and 7 of the "Update latest reading" algorithms would do that. But overall, I think we could replace this whole "reporting flag thing" by simply adding the whole "Update latest reading" in a new task.

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

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