Felipe G. writes: > Yeah, --e10s enables e10s in the browser for mochitest-chrome. However, > the test harness is a .xul file opened in a tab, and that runs that tab as > non-remote, so for most tests it ends up testing the same thing as not > using --e10s. Other tabs and/or windows opened manually by the test would > be remote.
What makes that first tab non-remote? I had guessed that documents from "chrome:" would run in the browser process (by default, at least), but is it all determined by attributes on a browser element? _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
