Change BrowserTestUtils synthesizeMouse/etc to handle out of process frames
Categories
(Testing :: Mochitest, task)
Tracking
(Fission Milestone:M4, firefox71 fixed)
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: enndeakin, Assigned: enndeakin)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
Attachments
(2 files)
This involves waiting for child iframes to load as well as being able to synthesize mouse/key events in child iframes.
Assignee | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Note that Kashav is currently working on some of these helper methods
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Note that bug 1559841 is needed to run some of the tests that use this.
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
I had this extra test_context_menu_iframe.js change in my password manager set of patches but it actually belongs here as it would otherwise fail.
Pushed by neil@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4b4202682c55 modify BrowserTestUtils.synthesizeMouse/Key/etc to handle fission. Remove support for passing arrays of selectors and instead modify the last argument to be a browsing context, or browser. Fix up tests that use this obsolete form, r=kmag https://hg.mozilla.org/integration/autoland/rev/d79153e62c0c change browser_context_menu_iframe.js to pass a browsing context for synthesizeMouse calls, also fixes test_context_menu_iframe_sandbox_same_origin test that was incorrectly using the wrong frame, r=MattN
Comment 7•5 years ago
|
||
Based on the following link, i think these changes have increased bug 1430977 frequency:
https://treeherder.mozilla.org/#/jobs?repo=autoland&searchStr=windows%2C10%2Cx64%2Cquantumrender%2Cdebug%2Cmochitests%2Ctest-windows10-64-qr%2Fdebug-mochitest-browser-chrome-e10s&fromchange=05273fba6dadc286c4b61baa77cce7bf599e41c0&tochange=f7d1df2061e77d556eb36fac6b87c629d12f4038&selectedJob=270044113
Neil, could you, please, take a look?
Assignee | ||
Comment 8•5 years ago
|
||
The browser_625016.js test fails for me locally every single time whether I have the changes in this bug applied or not. As my changes here are test-only changes unrelated to this failing test, I would instead suggest that that browser_625016.js is just broken entirely.
Comment 9•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4b4202682c55
https://hg.mozilla.org/mozilla-central/rev/d79153e62c0c
Updated•5 years ago
|
Description
•