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
Nicholas Nethercote
authored
There's no reason for them to be separate, and we can use the |kind| field to distinguish the two kinds when necessary. This lets us remove the duplication of ScriptableToString(), ToUTF8String(), and ScriptableEquals(). It also lets us use |Atom*| pointers instead of |nsIAtom*| pointers in various places within nsAtomTable.cpp, which de-virtualizes various calls and removes the need for some static_casts. --HG-- extra : rebase_source : 2f9183323446e353f8cc5dcedf57d9dc9a38f0a7