gecko-dev/devtools/docs
2019-06-04 12:44:57 +00:00
..
backend Bug 1042642 - Use EventEmitter instead of EventSource for the threadClient; r=jdescottes 2019-05-30 08:37:55 +00:00
contributing Bug 1553188 - Part 4 - Update remaining references to browser.xul;r=bdahl 2019-05-28 16:40:42 -07:00
files Bug 1429421 - remove gcli code; r=jdescottes,julienw,ochameau 2018-09-06 11:42:57 +00:00
frontend Bug 1527299 - Update devtools' Event Telemetry doc and example r=miker 2019-02-28 09:23:14 +00:00
getting-started Bug 1525289 - Use https:// on the repository url. r=sole 2019-03-01 05:21:48 +00:00
resources
styles
tests Bug 1556652 - Document how to create perf profiles on try for DAMP r=nchevobbe 2019-06-04 12:44:57 +00:00
tools bug 1504185 - remove highlighterUtils documentation from devtools; r=ochameau 2018-12-18 08:46:46 +00:00
.gitignore
about-documentation.md Bug 1508583 - Improve sections under getting started. r=ladybenko,Ola 2019-01-22 13:31:30 +00:00
bugs-issues.md
contributing.md Bug 1527826 - Reflect our github org name change in the m-c code; r=nchevobbe 2019-02-15 09:38:53 +00:00
preferences.md Bug 1527826 - Reflect our github org name change in the m-c code; r=nchevobbe 2019-02-15 09:38:53 +00:00
README.md Bug 1508583 - Improve sections under getting started. r=ladybenko,Ola 2019-01-22 13:31:30 +00:00
SUMMARY.md Bug 1531283: Add MOZ_QUIET description to explain how to disable ++DOMWINDOW and ++DOCSHELL logging r=sole 2019-02-28 12:02:44 +00:00

Firefox Developer Tools

NOTE: This is the documentation for working on the Developer Tools. If you are looking for help with using the tools, please check out the end user documentation instead.


Hello!

First of all, thank you for making it this far!

Developer Tools is a complex web application, and learning the code base will take some time, even if you're a very experienced contributor to other projects.

Likewise, getting and building the code locally, sending contributions for review, and other essential tasks can take a bit longer and be a bit different from what you're used to seeing.

But there are good news: most of the initial, lengthy tasks don't need to be repeated once your computer is set up. And there's a huge infrastructure in place (both technical and people) to ensure that many commits can land into the Firefox repository with the peace of mind that the code is peer reviewed, can be built and passes the tests, in multiple configurations and operating systems.

So don't be afraid of committing errors: you will. This is what happens to us all the time.

It's a big system, and no one knows absolutely everything. What we do know is that we are not going to break Firefox. If we do something wrong, the system will let us know before we mess things up for real. Users won't ever notice, and you will learn a new thing.

Let's get started.