1722714 - browser_max_touchpoints.js fails intermittently with server targets

Status: RESOLVED FIXED

(DevTools :: Responsive Design Mode, defect)

Description

[Alexandre Poirot [:ochameau]]

It fails with the following error (reproduced locally with --run-until-failure):

devtools/client/responsive/test/browser/browser_max_touchpoints.js
  FAIL navigator.maxTouchPoints should be 1 after enabling touch simulation again - Got +0, expected 1
Stack trace:
chrome://mochikit/content/browser-test.js:test_is:1371
chrome://mochitests/content/browser/devtools/client/responsive/test/browser/browser_max_touchpoints.js:null:43
chrome://mochitests/content/browser/devtools/client/responsive/test/browser/head.js:addRDMTaskWithPreAndPost/<:192

https://treeherder.mozilla.org/logviewer?job_id=346601765&repo=try&lineNumber=11365

Comment 2

[Nicolas Chevobbe [:nchevobbe]]

Attachment: Bug 1722714 - [devtools] Don't call restoreActorState from RDM client when target follow window global lifecycle. r=jdescottes.

The call to restoreActor state was inferring with the watcher setting up the configuration
on new documents, and was making browser_max_touchpoints and browser_touch_pointerevents
fail with server side target switching.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f8063f9fa56c
[devtools] Don't call restoreActorState from RDM client when target follow window global lifecycle. r=jdescottes.

Comment 4

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/f8063f9fa56c