814043 - [WebAPI] Device proximity sensor event 'min' and 'max' attribute values won't change

Status: RESOLVED WONTFIX

(Core :: DOM: Device Interfaces, defect)

Description

[Robert Wood [:rwood]]

Attachment: Proximity change marionette emulator test

The deviceproximity event 'min' and 'max' attributes always return '0' and '1' respectively.

To reproduce: Setup the 'deviceproximity' event listener. Issue the "sensor set proximity 7:3:15" command to the emulator to change the emulated proximity. Then the "sensor get proximity" command which verifies the emulator's proximity is now "7:3:15".

Wait for a 'deviceproximity' event, and notice the event.value has changed to '7' as expected, however the event.min is '0' (expected '3') and event.max is '1' (expected '15').

The attached test_proximity_change.js marionette emulator test will reproduce the issue.

Comment 1

[Doug Turner (:dougt)]

unassigning things that I am not working on.

Comment 2

[William Chen [:wchen]]

I have a suspicion that this bug and the attached test case is invalid. In particular, the emulator command "sensor set proximity 7:3:15" probably isn't doing what you think it's doing. I can't find any documentation for the "sensor set" emulator command but I'm guessing it's just setting the first three elements for sensor values array (http://developer.android.com/reference/android/hardware/SensorEvent.html#values). The proximity sensor only uses the first element (http://developer.android.com/reference/android/hardware/Sensor.html#TYPE_PROXIMITY), the second and third elements are not the min and max.