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

Re: [sensors] Relation to Feature Policy

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Thu, 23 Nov 2017 09:43:48 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-346570682-1511430226-sysbot+gh@w3.org>
@raymeskhoury, the key use cases are explained in the following WebKit bugs:

https://webkit.org/b/150072
https://webkit.org/b/152299

We will outline the use cases and justification in the Generic Sensor API specification per your suggestion. @alexshalamov @pozdnyakov, please take a note.

Related comment:

Since the work on DeviceOrientationEvent/DeviceMotionEvent spec [has stopped][1] we cannot add new features to that legacy specification (as was suggested in the WebKit bugs). The best we can do for that spec is to fix the remaining known issues to improve interoperability across browsers and allow the legacy spec finish its progress on the Recommendation track. This work is already underway, see https://github.com/w3c/deviceorientation/issues/46 and https://github.com/w3c/deviceorientation/issues/47.

Luckily we can add Feature Policy integration into the Generic Sensor API to address these important use cases developers are asking for to selectively enable sensors in cross-origin iframes, see https://github.com/w3c/sensors/pull/328.

[1]: https://www.w3.org/TR/orientation-event/#status
[2]: https://w3c.github.io/dap-charter/DeviceAPICharter.html#deliverables

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/sensors/issues/133#issuecomment-346570682 using your GitHub account
Received on Thursday, 23 November 2017 09:43:52 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 November 2017 09:43:52 UTC