Platform/Integration/InjectEject/Launcher Process/: Difference between revisions

Platform/Integration/InjectEject/Launcher Process/ (view source)

46 bytes added , 24 July 2019

no edit summary

98

edits

@@ Line 44: / Line 44: @@
 == Considerations for Developers ==
-* The launcher process is enabled by default both in local and CI builds. It may be disabled by specifying the <code>--disable-launcher-process</code> option in <code>mozconfig</code>. Leaving this as its default is preferred to ensure that the launcher process receives just as much testing as our other processes.
+* The launcher process is enabled by default both in local and CI builds. In local builds, the launcher process may be disabled by default by specifying the <code>--disable-launcher-process</code> option in <code>mozconfig</code>. Leaving this as its default is preferred to ensure that the launcher process receives just as much testing as our other processes.
 ** If you have disabled the launcher process by default in your local build, but would like to run it during a test, use the <code>-launcher</code> command-line option.
 * Both <code>mach run</code> and <code>mach gtest</code> automatically specify the <code>-wait-for-browser</code> option when starting Firefox. Visual Studio projects generated by the build system also automatically include this flag when running Firefox.