Confirm
286
edits
Changes
Some formatting changes and how to check for fission in browser mochitests
==General Tips==
* To run a mochitest with Fission enabled locally, use '<tt>--enable-fission’ fission</tt> with '<tt>mach test'</tt>. If the test is marked as a "fail-if" however, then you also need to disable that annotation. Otherwise, the test will report a false success (resulting from an expected fail). The skipped tests do not need this extra step.* <tt>SpecialPowers.useRemoteSubframes </tt> can be used to check if Fission is enabled from a mochitest. In browser mochitests, use <tt>gFissionBrowser</tt>.
* [https://searchfox.org/mozilla-central/rev/ec806131cb7bcd1c26c254d25cd5ab8a61b2aeb6/testing/specialpowers/content/SpecialPowersAPI.jsm#1366 SpecialPowers.spawn()] is typically used when you have a cross-process iframe and you need to interact with it in some way that is not supported cross-process. In such a case, one can use SpecialPowers.spawn() to send a script over to the process of the iframe to assert and/or return a value.
* If a test complains that the remote type is “webIsolated=<some URI>”, but it expected “web”, then you can use E10SUtils.isWebRemoteType() instead to check the remote type (added in [https://bugzilla.mozilla.org/show_bug.cgi?id=1574543 bug 1574543]).
