These are the tools provided by Firefox for developers to inspect Web code.

This repository is a hub that points to Developer Tools resources.

We abide by our code of conduct, and expect all contributors to do the same.

• End user guides.
• Developers documentation - here's an HTML version of these documents as well.
• Not strictly a roadmap, but these are some of our 2017 goals.

We publish news and updates to two blogs:

• Nightly for features newly added to Firefox Nightly. This is the place to request feedback from early adopters!
• Hacks when features reach more stable versions of Firefox.

You're more than encouraged to help us talk about the tools by writing an article, making a demo, or both! We wrote some guidelines for making demos.

There are various ways to get in touch with us:

• Bug reports or feature requests:
  • You can file bugs in Mozilla's bugzilla (please respect the etiquette).
  • or under each repository in devtools-html for code in GitHub
• The DevTools forum is a great way to get in touch with us and also ensure that your question is visible to other people (and hopefully help them as well).
• Mailing list: for people who prefer mail to forums.
• Team weekly video call: Vidyo room DevTools, Tuesdays 9AM Pacific time. The meeting doc has more details.
• IRC chat: #devtools channel in irc.mozilla.org, but bear in mind that perhaps the person that could help you best is not online when you ask the question. For that reason, it might be better to use the forum or mailing list instead.
• Contributors to debugger.html also hold periodic hangouts and have a slack channel.
• Twitter: @FirefoxDevTools.

Most changes will be done via either the "pick a bug and send a patch" or "send a PR" processes.

For substantial changes, we ask that a "request for comment" (RFC) document is provided first, so we can examine what the implications of a change will be. Here is how to follow the RFC process.

{% for person in site.github.organization_members %}

{{ person.login }}

{% endfor %}

The tools are broadly divided into panels. Each panel has one or more owners, who mostly work(s) on that panel and are the best people to ask if you have specific questions about the code.

• about:debugging: jdescottes, ochameau
• Animation Inspector: gl, pbro, daisuke
• Canvas Debugger: <unmaintained>
• Console: bgrins, nchevobbe
• Debugger: jlast
• Developer Toolbar: jwalker, mikeratcliffe
• DOM: honza
• Framework: Browser integration, toolbox and test infrastructure: jryans, bgrins, ochameau, honza
• Inspector: gl, pbro, zer0, jdescottes, tromey
• JSON Viewer: honza
• Memory: gregtatum
• Network Monitor: honza, rickychien, gasolin
• Performance: gregtatum
• Remote protocol and server infrastructure: jryans, ochameau
• Responsive Design Mode: jryans, zer0
• Scratchpad: jdescottes
• Shader Editor: <unmaintained>
• Style Editor: gl
• Storage Inspector: mikeratcliffe
• Themes: bgrins, ntim
• Web Audio Editor: <unmaintained>
• WebIDE: jryans, ochameau