036e6d2fa37a7d99a79ead610d33c719d8d56b79
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out changeset 647025383676 (bug1202902) Backed out changeset d70c7fe532c6 (bug1202902)
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
…
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
Backed out 2 changesets (bug
1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE
…
…
…
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:
http://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:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://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 http://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 -
http://nightly.mozilla.org/
Description
Languages
JavaScript
32.6%
C++
25.1%
HTML
20.9%
C
10.6%
Python
2.8%
Other
7.6%