From 92a1d6f512f566b30e0924d21a15ca621ceedd17 Mon Sep 17 00:00:00 2001 From: Alexander Shalamov Date: Tue, 26 Sep 2017 10:45:15 +0300 Subject: [PATCH] Remove duplicate Service Worker inline issue There is a dedicated issue in https://github.com/w3c/sensors/issues/12 --- index.bs | 6 ------ index.html | 10 +++------- 2 files changed, 3 insertions(+), 13 deletions(-) diff --git a/index.bs b/index.bs index ec7c860..8809c1d 100644 --- a/index.bs +++ b/index.bs @@ -378,12 +378,6 @@ To mitigate this threat, the user agent should check if it [=can expose sensor r whose [=active document=]'s [=steps to determine the visibility state|visibility state=] is "visible". -Issue: certain use cases require sensors to have background access. -Using a more complex {{PermissionDescriptor}}. -(e.g. with a boolean `allowBackgroundUsage = false`; [=dictionary member=]), -might be the solution to relax this restriction. - -

Permissions API

Access to [=sensor readings=] are controlled by the Permissions API [[!PERMISSIONS]]. diff --git a/index.html b/index.html index a7cf641..7ec5705 100644 --- a/index.html +++ b/index.html @@ -1843,10 +1843,6 @@

4.2.4. Visibility State

Sensor readings are only available in browsing contexts, whose active document's visibility state is "visible".

-

certain use cases require sensors to have background access. -Using a more complex PermissionDescriptor. -(e.g. with a boolean allowBackgroundUsage = false; dictionary member), -might be the solution to relax this restriction.

4.2.5. Permissions API

Access to sensor readings are controlled by the Permissions API [PERMISSIONS]. User agents use a number of criteria to grant access to the readings. @@ -2225,7 +2221,7 @@

[[identifyingParameters]] - A sensor type-specific group of dictionary members used to select the correct platform sensor to associate to this Sensor object. + A sensor type-specific group of dictionary members used to select the correct platform sensor to associate to this Sensor object.

7.1.3. Sensor.activated

@@ -2904,7 +2900,7 @@

identifying parameters. TODO: replace that by an abstract operation.

9.7. Extending the Permission API

-

An implementation of the Sensor interface for each sensor type must protect its reading by associated PermissionName or PermissionDescriptor. +

An implementation of the Sensor interface for each sensor type must protect its reading by associated PermissionName or PermissionDescriptor. A Low-level sensor may use its interface name as a PermissionName, for instance, "gyroscope" or "accelerometer". Fusion sensors must request permission to access each of the sensors that are used as a source of fusion.

@@ -2914,7 +2910,7 @@

request permission to use magnetometer as it provides information about orientation of device in relation to Earth’s magnetic field. In contrast, relative orientation sensor does not expose such information, thus, it does not need to request permission to use magnetometer.

-

Permission descriptors can also be used to set maximum allowed limits +

Permission descriptors can also be used to set maximum allowed limits for accuracy or sampling frequency. An example for a possible extension of the Permission API for accelerometer sensor is given below.

dictionary AccelerometerPermissionDescriptor : PermissionDescriptor {