Closed Bug 924097 Opened 11 years ago Closed 5 years ago

Geolocation test failures (test_timerRestartWatch.html) caused by the fix for bug 684722

Categories

(Core :: DOM: Geolocation, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: mjh563, Unassigned)

References

Details

The proposed fix for bug 684722 has exposed an issue with the testing system that causes some mochitests that use stop_geolocationProvider to fail.

This happens because stop_geolocationProvider doesn't actually stop the provider making XHR calls, it just causes the server to return an empty response. Currently the provider ignores these empty responses, but in bug 684722 it will (correctly) notify an error back to the Geolocation service.

This causes timeout tests like test_timerRestartWatch.html to fail, because they assume that after calling stop_geolocationProvider, no further notifications will be sent from the provider.

The solution is to stop the provider making XHR calls in this situation. For example, it could check if testing is enabled and the URL contains "?action=stop-responding", and if so then not run the XHR.
We might be able to work around this by calling `response.processAsync()` before returning. I think this should keep the connection open and avoid sending a response, allowing for the timeout to be called.
Summary: Geolocation test failures caused by the fix for bug 684722 → Geolocation test failures (test_timerRestartWatch.html) caused by the fix for bug 684722

If this is still happening we can re-open, but based on the age and lack of activity I'll mark this inactive.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.