testing/mochitest/mochitest-e10s-utils-content.js@6474c204b198 (annotated)
testing/mochitest/mochitest-e10s-utils-content.js
Wed, 31 Dec 2014 06:09:35 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Wed, 31 Dec 2014 06:09:35 +0100
- changeset 0
- 6474c204b198
- permissions
- -rw-r--r--
Cloned upstream origin tor-browser at tor-browser-31.3.0esr-4.5-1-build1
revision ID fc1c9ff7c1b2defdbc039f12214767608f46423f for hacking purpose.
| michael@0 | 1 | // This is the content script for mochitest-e10s-utils |
| michael@0 | 2 | |
| michael@0 | 3 | // We hook up some events and forward them back to the parent for the tests |
| michael@0 | 4 | // This is only a partial solution to tests using these events - tests which |
| michael@0 | 5 | // check, eg, event.target is the content window are still likely to be |
| michael@0 | 6 | // confused. |
| michael@0 | 7 | // But it's a good start... |
| michael@0 | 8 | ["load", "DOMContentLoaded", "pageshow"].forEach(eventName => { |
| michael@0 | 9 | addEventListener(eventName, function eventHandler(event) { |
| michael@0 | 10 | // Some tests also rely on load events from, eg, iframes, so we should see |
| michael@0 | 11 | // if we can do something sane to support that too. |
| michael@0 | 12 | if (event.target == content.document) { |
| michael@0 | 13 | sendAsyncMessage("Test:Event", {name: event.type}); |
| michael@0 | 14 | } |
| michael@0 | 15 | }, true); |
| michael@0 | 16 | }); |
