- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 May 2017 17:19:50 +0000
- To: public-device-apis-log@w3.org
> Whole section if pretty normative, with must + dedicated algorithm. Sorry, thought you were talking about the note in the algo itself. Filed #226 to fix that issue. > We do, it is implemented properly in Chromium and @pozdnyakov is trying to clean-up spec, so it will be implementable by other vendors (EDIT: implementable => implementable by other vendors :D Chromium is fine). Right, but the spec says nothing about that for now, so that's not relevant here. > I don't understand you :) Sometimes you are worried about small things that do not affect performance, You're mixing up implementation optimization, which is not the spec's business, with normative spec content which might force implementations or web developers to use patterns with known performance issues, which _is_ the spec business. In particular when that's been flagged by the TAG as an issue. > while you are leaving pretty serious performance issues as 'may' requirement. Again, please see: https://w3c.github.io/sensors/#equivalent. > 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. Again, that's an implementation optimization. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/pull/213#issuecomment-304948059 using your GitHub account
Received on Tuesday, 30 May 2017 17:19:57 UTC