It can do some more.
hemanth opened this issue · 6 comments
Physical Web (Android)
Device Motion and Orientation (all)
Gamepad (all -ChromeOS)
Web NFC is there already and some of the new generic sensors (not all yet)
magnetometer, accelerometer, gyroscope, barometer, thermostat, hygrostat. right?
barometer, thermostat, hygrostat spec are not public yet as they are not in the W3C working group charter, but we might make them unofficial drafts soon and then later recharter. This will be discussed at the yearly W3C TPAC meeting next week
ambient light sensor as well
More sensors will be described soon. By now there is Proximity Sensor, Ambient Light Sensor, Accelerometer & Gyroscope described.
Device Motion and Device Orientation are already described, too.
Gamepad API looks interesting and has a decent support. Will take a look in the next series of updates.
For Physical Web, I'm not sure whether I should handle that. If I understand that thing correctly, it's a custom protocol implemented over Bluetooth LE and is not a part of any specification, am I correct? As such it can theoretically be handled by Bluetooth API manually and the actual capability is the Bluetooth support, that is already described, but with some additional usability fixes and shortcuts in Chrome. Is that a generic web capability, potentially implemented by others as a thing separate from Bluetooth etc.? It looks for me it's too early to guess. But I might be totally wrong here.