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

Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.

From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
Date: Tue, 30 May 2017 16:51:06 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-304939709-1496163064-sysbot+gh@w3.org>
> That's a non-normative note encouraging implementations to optimize resource consumptions here granted they meet spec requirements.

Whole section if pretty normative, with must + dedicated algorithm.

> So they're not firing onchange now, nor are they creating tasks right now, because as you noticed, neither's hooked-up properly. :)

We do, it is implemented properly and @pozdnyakov is trying to clean-up spec, so it will be implementable.

> That's an implementation detail. You're encouraged to optimize as long as you meet the requirements.

I don't understand you :) Sometimes you are [worried](https://github.com/w3c/sensors/issues/198#issuecomment-304275605) about small things that do not affect performance, while you are leaving pretty serious performance issues as 'may' requirement.

> See: https://w3c.github.io/sensors/#equivalent. You should obviously be caching the result of this algorithm and be invalidating the cache as conditions change.

Problem is that algorithm is in a wrong place and does not do what it should do, suspending sensor when data should not be provided.

Could you please reopen #217 and #189. We can specify required operations properly and align with implementation.

-- 
GitHub Notification of comment by alexshalamov
Please view or discuss this issue at https://github.com/w3c/sensors/pull/213#issuecomment-304939709 using your GitHub account
Received on Tuesday, 30 May 2017 16:51:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC