W3C home > Mailing lists > Public > public-device-apis-log@w3.org > March 2018

[sensors] Define mechanism for forward compatibility checks

From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
Date: Wed, 21 Mar 2018 08:41:30 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-307157117-1521621688-sysbot+gh@w3.org>
alexshalamov has just created a new issue for https://github.com/w3c/sensors:

== Define mechanism for forward compatibility checks ==
Generic Sensor API requires UA to feature detect [supported sensor options](https://w3c.github.io/sensors/#supported-sensor-options)

> The user agent must remove items from supported sensor options for a given extension sensor interface if it cannot support the corresponding sensor options.

However, due to the https://github.com/heycam/webidl/issues/107, it is not possible to implement (_"in a clean way"_) forward compatibility check for a sensor options that contain new features.

Chromium bug: [823223](https://bugs.chromium.org/p/chromium/issues/detail?id=823223)
Issue that was raised by @anssiko when new sensor option was specified: https://github.com/w3c/sensors/issues/257#issuecomment-359487879

Please view or discuss this issue at https://github.com/w3c/sensors/issues/361 using your GitHub account
Received on Wednesday, 21 March 2018 08:41:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 March 2018 08:41:36 UTC