This has been driving me nuts, and it turns out to be so simple, and so stupid. And I could do the right thing, and not see the symptom. But it points to a bigger problem (perhaps) with case sensitivity in resource names on a Mac. If people start using case-sensitive file systems, we will have unusual problems. I can launch Firefox on the command line with this: /Users/ray/mo/trowser/mozilla/dist/Minefield.app/Contents/Macos/firefox -P minefield1 This launches the app, but when one switches to the Minefield window, the menus still say Terminal and no key presses are accepted in the browser window. They all go to Terminal. Launch Firefox this way and it works fine: /Users/ray/mo/trowser/mozilla/dist/Minefield.app/Contents/MacOS/firefox -P minefield1 If nothing else, we should understand why launching with the first call breaks so weirdly.
10 years later, confirming that this problem still occurs as of FF 49. The upcoming Sierra file system is case sensitive. Will parts of FF handle it inconsistently?
You need to log in before you can comment on or make changes to this bug.