With the fix for bug 1494326[1] (on autoland), when run on macOS, "mach run" has a new option "--macos-open" to launch the browser using the open(1) command. Note --macos-open and --debug are mutually exclusive and mach will exit with an error if both options are used.
Per the open(1) man page, "the open command opens a file (or a directory or URL), just as if you had double-clicked the file's icon." One big difference is that the application is spawned directly by the launchd process instead of via the shell parent process chain. There is no support for using this with tests, but there is an argument to be made that our testing would be more representative of real world use if we started the browser in the same way that users do. That would require reworking tests to wait for the correct browser process to exit and somehow collecting stdout/stderr output. That might be something we do in the future if the option ends up being useful. One use I've found for this relates to the new macOS 10.14 Mojave device permission dialogs for the camera/mic. When launched via "mach run", the dialog is displayed as '"Terminal" would like to access the camera." (I consider that a macOS limitation and not a Firefox bug.) When launching with the open command, the dialog is displayed correctly. Thanks, Haik 1. https://bugzilla.mozilla.org/show_bug.cgi?id=1494326 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
