When firing null-events stop DeviceSensorEventController only after the event has propagated to win…

When firing null-events stop DeviceSensorEventController only after the event has propagated to window.

When no sensors are available chrome should fire an all-null event
into blink. However at the time of firing the active DOM objects
can be suspended or stopped, which can prohibit propagation of the
event to window. Currently the controller will be unregistered in
any case because the event is a null-event. This results in the
potential loss of null-events and the javascript callback is never
executed. To avoid this issue the firing of a null-event should
happen until it effectively propagates to window.

BUG=356750
TEST=http://jsbin.com/pivimoga/1/ (manual)
TEST=https://codereview.chromium.org/214763002/ (browsertest)

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=170200

[abarth-chromium, 2014-03-27 03:30:17]

Test?

[abarth-chromium, 2014-03-27 03:30:27]

lgtm assuming you add a test

[timvolodine, 2014-03-27 14:55:26]

On 2014/03/27 03:30:27, abarth wrote:
> lgtm assuming you add a test

Thanks Adam. Not sure if this can be tested using layout tests, because the mock
test events there are echoed only once. Instead I have content browsertests to
cover this issue, i.e. https://codereview.chromium.org/214763002/.

[timvolodine, 2014-03-27 19:04:36]

The CQ bit was checked by timvolodine@chromium.org

[commit-bot: I haz the power, 2014-03-27 19:04:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/timvolodine@chromium.org/212983007/1

[commit-bot: I haz the power, 2014-03-27 20:03:06]

Change committed as 170200