gecko-dev/devtools/docs
Tom Ritter e751bb508a Bug 1592297 - Remove MOZ_QUIET and disable this output by default. r=mccr8,jdescottes
Instead of setting MOZ_QUIET to hide the DOMWINDOW and DOCSHELL log messages, you
now must set a regular logging module to enable them. They are automatically enabled
on tests that rely on these messages are leak checking.

That module is DocShellAndDOMWindowLeak:3

One disadvantage of this change is that you cannot set MOZ_QUIET to hide these
messages when running those tests (primarily browser-chrome).

Differential Revision: https://phabricator.services.mozilla.com/D52413

--HG--
extra : moz-landing-system : lando
2019-12-02 15:41:35 +00:00
..
backend Bug 1519103 - Remove Scratchpad panel. r=bgrins. 2019-10-27 09:05:58 +00:00
contributing Bug 1596342 - Update sending patch documentation to only mention Phabricator + moz-phab. r=rcaliman. 2019-11-14 16:49:44 +00:00
files
frontend
getting-started Bug 1519103 - Remove Scratchpad panel. r=bgrins. 2019-10-27 09:05:58 +00:00
resources
styles Bug 1596911 - Add missing license headers on the new managed extensions r=Gijs,MattN 2019-11-26 15:00:00 +00:00
tests Bug 1592297 - Remove MOZ_QUIET and disable this output by default. r=mccr8,jdescottes 2019-12-02 15:41:35 +00:00
tools Bug 1599027 - Remove http inspector doc. r=Honza. 2019-11-26 08:43:59 +00:00
.gitignore
README.md
about-documentation.md
book.json
bugs-issues.md
contributing.md
index.md Bug 1592297 - Remove MOZ_QUIET and disable this output by default. r=mccr8,jdescottes 2019-12-02 15:41:35 +00:00
preferences.md

README.md

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.