sensors
sensors copied to clipboard
w3c
Generic Sensor API
> [Sensor readings](https://www.w3.org/TR/generic-sensor/#sensor-reading) are only available for [active documents](https://html.spec.whatwg.org/multipage/browsers.html#active-document) whose origin is [same origin-domain](https://html.spec.whatwg.org/multipage/origin.html#same-origin-domain) with the [currently focused area](https://html.spec.whatwg.org/multipage/interaction.html#currently-focused-area-of-a-top-level-browsing-context) document. In Compute Pressure we do the following: > Let |topLevelBC|...
> The current [browsing context](https://html.spec.whatwg.org/multipage/browsers.html#browsing-context)'s [platform sensor](https://www.w3.org/TR/generic-sensor/#concept-platform-sensor) has an associated [set](https://infra.spec.whatwg.org/#ordered-set) of activated sensor objects, which is initially [empty](https://infra.spec.whatwg.org/#list-is-empty) and an associated latest reading [map](https://infra.spec.whatwg.org/#ordered-map), which holds the latest available ...
We should check that the spec complies with https://w3ctag.github.io/design-principles/#support-non-fully-active Given https://w3c.github.io/sensors/#can-expose-sensor-readings is conditional to https://html.spec.whatwg.org/multipage/interaction.html#currently-focused-area-of-a-top-level-browsing-context (among other checks) we may be good. @marcoscaceres is probably interested in this design discussion.
We should properly specify the constructor algorithm and internal slots for `SensorErrorEvent`: https://www.w3.org/TR/generic-sensor/#the-sensor-error-event-interface
The constructors of concrete sensor specs invoke "Construct a FooSensor object" abstract operation (e.g. [accelerometer](https://w3c.github.io/accelerometer/#construct-an-accelerometer-object) and [gyroscope](https://w3c.github.io/gyroscope/#construct-a-gyroscope-object)) that in turn invokes [Check sensor policy-controlled features](https://w3c.github.io/sensors/#check-sensor-policy-controlled-features) defined in the Generic Sensor...
Hi, I don't know if this is the right place for this but i would like to have some API for working together with my remote IR controller to control...
I think this is what you meant. The old text in Mitigations, "the currently focused area document", doesn't have a meaning. The text in "mandatory conditions" was better, but isn't...
Discussions of the privacy considerations of this API have floated the idea of a low-resolution mode which does not require a permission, and a high-resolution mode that does. While the...
According to the spec, if a sensor type has more than one sensor it has a set of [identifying parameters](https://w3c.github.io/sensors/#identifying-parameters). How this is going to be implemented is not entirely...
Browsers only sample sensor data at a varying 67Hz (drops down to 1Hz sometimes), which makes the readings unusable for high end use cases... We need a robust 120Hz steady...
