An explanation of the Mozilla Source Code Directory Structure and links to project pages with documentation can be found at: https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure For information on how to build Mozilla from the source code, see: https://developer.mozilla.org/en/docs/Build_Documentation To have your bug fix / feature added to Mozilla, you should create a patch and submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at: https://developer.mozilla.org/en/docs/Creating_a_patch https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree If you have a question about developing Mozilla, and can't find the solution on https://developer.mozilla.org, you can try asking your question in a mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups are accessible on Google Groups, or news.mozilla.org with a NNTP reader.] You can download nightly development builds from the Mozilla FTP server. Keep in mind that nightly builds, which are used by Mozilla developers for testing, may be buggy. Firefox nightlies, for example, can be found at: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ - or - https://nightly.mozilla.org/
Forked from
The Tor Project / Applications / Tor Browser
430587 commits behind the upstream repository.
Kris Maglione
authored
User preference changes currently don't reliably take effect before component loader initialization, which means they can't be used to write reliable tests. Environment variables don't have this problem, so adding an environment variable override makes testing much easier. It's also fairly convenient during development, when we need to switch between different configurations for testing. MozReview-Commit-ID: 8PufRQNRnoU --HG-- extra : rebase_source : c5ca2f3cb18a8398c95bbbf86e2cd27430f5161a