MozillaWiki - User contributions [en]

Modules/Other

2020-03-23T10:49:43Z

Pbrosset: Updated the DevTools owner as announced here https://groups.google.com/forum/#!topic/mozilla.governance/OGhrKw6ysts

Modules/Other

2020-03-17T07:00:28Z

Pbrosset: Adding the owners emeritus section and adding dcamp and robcee to it

Modules/Other

2020-03-17T06:22:23Z

Pbrosset: Added a couple missing DevTools peers, and removed some who haven't been active on the codebase for a long time

Modules/Other

2020-01-31T11:56:17Z

Pbrosset: Moved Jan Keromnes to peers emeritus after talking to him about it

Modules/Other

2020-01-23T08:23:42Z

Pbrosset: Removed Lin from the list of devtools peers after talking to her

Modules/Other

2020-01-21T17:36:27Z

Pbrosset: More changes to devtools peers after talking to people

Modules/Other

2020-01-21T16:15:41Z

Pbrosset: Removed Victor Porof from the devtools peers list after talking to him

Modules/Other

2020-01-21T08:13:44Z

Pbrosset: Moved Paul Rouget to DevTools' peer emeritus list, and re-ordered the list of peers

Modules/Other

2020-01-20T08:08:49Z

Pbrosset: Add more info about what part of the code fitzgen is still ok to review

Modules/Other

2020-01-17T16:18:15Z

Pbrosset: Moving Tom Tromey to the list of devtools peers emeritus, after talking to him

Modules/Other

2020-01-17T14:59:51Z

Pbrosset: Moving Jaroslav Šnajdr to the list of devtools peers emeritus, after talking to him

Modules/Other

2020-01-17T13:25:23Z

Pbrosset: Moving a DevTools peer to peers emeritus

ExposureGuidelines

2019-07-22T15:57:08Z

Pbrosset: Updated the devtools bugzilla link on that page

=Adding features=

One way Mozilla aims to advance the state of the web platform is with new features. Always ask: ''Is this good for the web?''

If you aim to expose a new feature to the web or change an existing feature, please follow these steps:

# Email [https://lists.mozilla.org/listinfo/dev-platform dev-platform] declaring your [[#Intent to prototype|intent to prototype]]. (It is okay to skip this step for small changes.)
## If you are implementing a feature that is working its way through a standards body process such as the W3C's, it's best to email as soon as possible (i.e., before [http://www.w3.org/2005/10/Process-20051014/tr#q74 W3C CR status] if possible).
# Implement as normal. Code review rounds will take place, etc. Module owners or their designated peers will provide a super-review for all interface changes.
## [https://blog.mozilla.org/security/2018/01/15/secure-contexts-everywhere/ Restrict the feature to secure contexts].
## Ensure the feature has [https://github.com/w3c/web-platform-tests web-platform-tests] coverage.
## Land potentially disruptive features behind a preference which is off by default.
# Email [https://lists.mozilla.org/listinfo/dev-platform dev-platform] declaring your [[#Intent to ship|intent to ship]].
# If there's no negative feedback, ship.

==Intent to prototype==

'''To''': <tt>dev-platform@lists.mozilla.org</tt> 
'''Subject''': Intent to prototype: <your feature goes here>

''Summary'': [https://en.wikipedia.org/wiki/Elevator_pitch elevator pitch] for the new functionality including benefits to web developers. 
''Bug'': link to Bugzilla (tracking) bug. 
''Standard'': link to standard or link to public discussions with other browser vendors. 
''Platform coverage'': where will this be available? Android, Desktop, only exposed to privileged apps (certified app-only functionality does not require an email), etc. 
''Preference'': if applicable, how can interested parties test this before it ships pref'd on by default? 
''DevTools bug'': link to a [https://bugzilla.mozilla.org/enter_bug.cgi?product=devtools Developer Tools bug] coordinating work with the DevTools team to build tools for this feature. 
''Other browsers'': address with "shipped" (since version X, behind what flags if any), "intent emailed" (mailing list URL), or "considering" (citation). 
''web-platform-tests'': Please link to the test suite. If any part of the feature is not tested by web-platform-tests, please include links to one or more of:
* A web-platform-tests issue explaining why a certain thing cannot be tested ([https://github.com/w3c/web-platform-tests/issues/3867 example]).
* A spec issue for some change that would make it possible to test ([https://github.com/whatwg/fullscreen/issues/70 example]).
* A Bugzilla bug for the creating web-platform-tests.
''Secure contexts'': Provide justification if this feature is not restricted to secure contexts. Otherwise, use "Yes".
''Is this feature enabled by default in sandboxed iframes?'' If not, is there a proposed sandbox flag to enable it? If allowed, does it preserve the current invariants in terms of what sandboxed iframes can do? 

===Suggested additions===

The above is the minimum required that should be in an "Intent to prototype" email. If you've covered those, you're good, and brevity is a virtue.

If you're looking for extra credit, or to preempt common questions, consider adding any or all of the following (all based on existing dev-platform examples, and questions asked on dev-platform in response to intent to ship emails).
* ''Link to standards-positions discussion'': Link to a discussion in [https://github.com/mozilla/standards-positions mozilla/standards-positions] about what we think about the specification.
* ''How stable is the spec'': Note that even if it's unstable that shouldn't stop us implementing; that mostly affects shipping. So as long as we're pretty sure that the basic set of functionality is stable, even if the actual names of the values are not, implementing makes sense.
* ''Security & Privacy Concerns'': consider providing a link to answers in [https://mikewest.github.io/spec-questionnaire/security-privacy/ this security/privacy questionnaire] for a spec feature, if the spec doesn't already answer it. In particular, consider if the spec exposes new information about a user's computer or behavior that can contribute to fingerprinting.
* ''Web designer / developer use-cases'' AKA ''Why a developer would use Feature X?'': Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate why and when they would use this feature.
* ''Example'': Provide a brief code sample on how to use the API. Even with a formal specification, not everyone will know about the feature just from the name of the spec. An example will make it easier to understand how this feature can be used. This can either be an inline code sample, or a direct link to an example on the web.

==Intent to ship==

'''To''': <tt>dev-platform@lists.mozilla.org</tt> 
'''Subject''': Intent to ship: <your feature goes here>

As of <target date> I intend to turn <feature> on by default [<on these platforms>]. It has been developed behind the <pref> preference. Other UAs shipping this or intending to ship it are <details>.

''Bug to turn on by default'': link to main relevant bug (https://bugzilla.mozilla.org/show_bug.cgi?id=) ['''note''': this bug should ideally have the ''dev-doc-needed'' keyword set] 

This feature was previously discussed in this "Intent to prototype" thread: <https://groups.google.com/forum/#!forum/mozilla.dev.platform>. '''If anything changed since that thread please include that information in this email'''.

It's acceptable to merge the "intent to prototype" into the "intent to ship" email as long as all the relevant requirements are met.

=Removing features=

Occasionally there is a need to remove features. These could be features that are proprietary to Mozilla, were standardized but never got adopted by all browsers, or features that are so bad that all browsers want to get rid of them together.

In order to make this possible while impacting users as little as possible the following steps are to be taken:

* Gather telemetry on the feature.
* Consult dev-platform with an [[#Intent to unship|intent to unship]] that includes the telemetry data.
* Indicate in the developer console whenever the feature is used that it's deprecated and might be removed. It's best to avoid doing this until there's agreement that the feature can be removed (which requires telemetry) as otherwise developers are needlessly spammed in the console.
* Remove the feature when the telemetry data and dev-platform agreement indicate it can be.

==Intent to unship==

'''To''': <tt>dev-platform@lists.mozilla.org</tt> 
'''Subject''': Intent to unship: <your feature goes here>

<The body of the email should contain rationale, telemetry analysis, links to related discussions if any, and developer console suggestions.>

= See Also =
* [[WebAPI/DesignGuidelines]]
* [[WebAPI/WebIDL_Review_Checklist]]
* [https://www.chromium.org/blink Chrome/Blink change process]
** [https://www.chromium.org/blink/launching-features Chrome/Blink process for Launching Features] in particular

=FAQ=

==When is a feature ready to ship?==

Features which Mozilla makes available by default to the web on the release channel should be "ready". This can mean that they are de jure standards (e.g., a W3C Recommendation) or de facto standards. Indications that a feature is ready for shipping to the web include:

# other browser engines ship compatible implementations in their releases or behind a preference with clear signals it will graduate to being on by default
# other browser engines state their ''intention'' to ship a compatible implementation
# a large number of web developers indicate their satisfaction with the feature design
# there exists a specification that is no longer at risk of significant changes, is on track to become a standard with a relevant standards body, and is acceptable to a number of applicable parties and other browser engines

==How do we know what web developers want?==

* Mozilla's [[Engagement/Developer_Engagement|Developer Engagement]] coordinates a [https://openwebapps.uservoice.com/forums/258478-open-web-apps Open Web Apps UserVoice] forum
* [http://chromestatus.com chromestatus.com] has a column for new features entitled "Documented or perceived web developer views"

==How do we know what other browser engines think?==

* Some of them participate in dev-platform discussions
* Watch for positive signals on the specification's discussion forum (likely a GitHub repository)
* Watch for "intent to *" emails on mailing lists such as [https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev blink-dev]

Note: lack of feedback will not delay our implementation as it may simply indicate lack of interest at that time from another browser engine.

==How do we let other browser engines know what we think?==

* By documenting our position on [standards-positions https://github.com/mozilla/standards-positions].
* Participating in public discussions of new features.
* Comment on "intent to *" threads on [https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev blink-dev].

==What about prefixes?==

In the past, Mozilla has shipped experimental features with a "moz" prefix to indicate their lack of standardization (e.g., <code>mozRequestAnimationFrame()</code>). Unfortunately, this approach turned out to be harmful to the web as experimental features ended up being used in some websites before they were ready. In many cases, this meant that we were unable to innovate on certain features because to change them would break content on the web. Browsers have in some cases also been [https://compat.spec.whatwg.org/ forced to implement each other's prefixed features]. Therefore, to allow us to continue innovating without negatively affecting content on the web, '''Mozilla will no longer ship new "moz"-prefixed features''' (see [https://groups.google.com/forum/#!topic/mozilla.dev.platform/34JfwyEh5e4 Henri Sivonen's proposal]).

We will instead prototype features behind preferences which can be toggled through <code>about:config</code>. Once we feel there is an acceptable level of consensus in the web community about the stability of an feature and we feel it is ready, we will make it generally available to the web platform (more details below on this process). We feel this strikes the right balance between allowing developers to experiment with new features, while at the same time protecting the web from being exposed to new functionality prematurely.

==Who decides?==

If the dev-platform thread results in a conflict, the respective [[Modules|module owner]] is responsible for resolving that conflict and making a decision on how to proceed.

Modules/Other

2018-11-08T08:27:57Z

Pbrosset: Updated DevTools peers

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Add-on SDK
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Myk Melez, Will Bamberg
|forum=http://groups.google.com/group/mozilla-labs-jetpack
|source_dirs=https://github.com/mozilla/addon-sdk
|url=https://wiki.mozilla.org/Jetpack
|components=Add-on SDK
}}

{{Module
|name=Android Background Services
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.
|owner=[mailto:rnewman@mozilla.com Richard Newman]
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox]
|forum=mozilla.dev.platforms.mobile
|source_dirs=https://github.com/mozilla-services/android-sync
|url=https://wiki.mozilla.org/Android/Services
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]
}}

{{Module
|name=BrowserID
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..)
|owner=Ben Adida
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons
|source_dirs=
BrowserID server code: https://github.com/mozilla/browserid,
BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity
|forum=https://lists.mozilla.org/listinfo/dev-identity
}}

{{Module
|name=ChatZilla
|description=IRC client
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]
|group=dev-apps-chatzilla
|source_dirs=extensions/irc/
|url=http://chatzilla.hacksrus.com/
|components=Other Applications::ChatZilla
}}

{{Module
|name=Composer
|description=Editor/Composer
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-tech-editor
|source_dirs=editor/
|url=http://www.mozilla.org/editor
|components=Composer
}}

{{Module
|name=Content Services Infrastructure
|description=A set of data services that allow for content to be served and measured
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]
|peers=[mailto:tspurway@mozilla.com Tim Spurway]
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx
|url=https://wiki.mozilla.org/Tiles
|components=Content Services
}}

{{Module
|name=DevTools
|description=Mozilla Developer Tools
|owner=[mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jwalker@mozilla.com Joe Walker]
|peers=[mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes],[mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:jsantell@mozilla.com Jordan Santell], [mailto:ttromey@mozilla.com Tom Tromey], [mailto:jsnajdr@gmail.com Jaroslav Šnajdr], [mailto:lclark@mozilla.com Lin Clark], [mailto:jlaster@mozilla.com Jason Laster], [mailto:odvarko@gmail.com Jan 'Honza' Odvarko], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:chevobbe.nicolas@gmail.com Nicolas Chevobbe], [mailto:ystartsev@mozilla.com Yulia Startsev], [mailto:sole@mozilla.com Soledad Penadés], [mailto:jwajsberg@mozilla.com Julien Wajsberg], [mailto:rcaliman@mozilla.com Razvan Caliman], [mailto:mtigley@mozilla.com Micah Tigley], [mailto:sfink@mozilla.com Steve Fink] (heapsnapshot code)
|peersemeritus=Mihai Șucan, Rob Campbell, Heather Arthur, Anton Kovalyov, Brandon Benvie, Eddy Bruel, James Long, Matteo Ferretti
|group=dev-developer-tools
|source_dirs=devtools
|url=https://wiki.mozilla.org/DevTools
|components=Firefox::Developer Tools
}}

{{Module
|name=Directory SDK
|description=Tools and SDKs for accessing LDAP Directories.
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]
|group=dev-tech-ldap
|source_dirs=directory/
|url=http://www.mozilla.org/directory
|components=Directory
}}

{{Module
|name=DOM Inspector
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=
|source_dirs=extensions/inspector/, layout/inspector/
|url=
|components=Other Applications::DOM Inspector
}}

{{Module
|name=Firefox for Android (Fennec)
|description=Mobile Web Browser
|owner=[mailto:snorp@mozilla.com James Willcox (:snorp)], [mailto:sebastian@mozilla.com Sebastian Kaspari (:sebastian) ]
|peers=[mailto:rnewman@mozilla.com Richard Newman (:rnewman)], [mailto:liuche@mozilla.com Chenxia Liu (:liuche)], [mailto:nalexander@mozilla.com Nick Alexander (:nalexander)], [mailto:mcomella@mozilla.com Michael Comella (:mcomella)], [mailto:gkruglov@mozilla.com Grisha Kruglov (:grisha)], [mailto:maliu@mozilla.com Max Liu (:maliu)], [mailto:nechen@mozilla.com Nevin Chen (:nechen)], [mailto:jchu@mozilla.com Julian Chu (:walkingice)]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=mobile/
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for Android
}}

{{Module
|name=Firefox for iOS (Fennec)
|description=Mobile Web Browser
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:sleroux@mozilla.com Steph Leroux], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=https://github.com/mozilla/firefox-ios
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for iOS
}}

{{Module
|name=Firefox Accounts
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.
|owner=[mailto:rfkelly@mozilla.com Ryan Kelly]
|peers=[mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:pbooth@mozilla.com Phil Booth], [mailto:vbudhram@mozilla.com Vijay Budhram]
|group=
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts
}}

{{Module
|name=Firefox for Metro
|description=Touch-screen-friendly browser for Windows
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]
|forum=https://mail.mozilla.org/listinfo/metro
|source_dirs=browser/metro
|url=https://wiki.mozilla.org/Firefox/Metro
|components=Firefox for Metro
}}

{{Module
|name=Loop aka Firefox Hello
|description=Voice and Video Collaboration System
|owner=[mailto:standard8@mozilla.com Mark Banner]
|peers=[mailto:abr@mozilla.com Adam Roach], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client
|url=https://wiki.mozilla.org/Loop
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop
}}

{{Module
|name=Mozilla Location Service (MLS)
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]
|peers=
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/ichnaea
|url=https://location.services.mozilla.com
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues
}}

{{Module
|name=Mozilla Stumbler ("MozStumbler")
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).
|owner=Garvan Keeley
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/MozStumbler
|url=https://location.services.mozilla.com
|components=https://github.com/mozilla/MozStumbler/issues
}}

{{Module
|name=Sync
|description=Firefox Sync client
|owner=[mailto:mconnor@mozilla.com Mike Connor]
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen
|group=
|source_dirs=services/sync/
|url=https://wiki.mozilla.org/Services/Process/Code_Review
|components=Sync
}}

{{Module
|name=Party Tool
|description=PHP-based party tool used for Firefox Party
|owner=[mailto:rflint@ryanflint.com Ryan Flint]
|peers=Mike Morgan, [mailto:reed@reedloden.com Reed Loden]
|group=dev-apps-webtools
|source_dirs=webtools/partytool/
|url=http://wiki.mozilla.org/Webtools:PartyTool
|components=
}}

{{Module
|name=Penelope
|description=Eudora-like functionality and theme added to Thunderbird.
|owner=Jeff Beckley
|peers=
|group=
|source_dirs=penelope/
|url=https://wiki.mozilla.org/Penelope
|components=Penelope
}}

{{Module
|name=Popcorn.js
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/popcorn-js/
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview
}}

{{Module
|name=Popcorn Maker
|description=An SDK for authoring Popcorn projects.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/butter/
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview
}}

{{Module
|name=Rhino
|description=JavaScript interpreter/compiler implemented in Java
|owner=[mailto:greg@apigee.com Greg Brail]
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]
|group=dev-tech-js-engine
|source_dirs=js/rhino/
|url=http://www.mozilla.org/rhino/
|components=Rhino
}}

{{Module
|name=Screenshots
|description=Code relating to Screenshots functionality, both client (eg. Firefox) and server.
|owner=[mailto:ianb@mozilla.com Ian Bicking]
|peers=[mailto:jhirsch@mozilla.com Jared Hirsch], [mailto:bchen@mozilla.com Barry Chen], [mailto:pdahiya@mozilla.com Punam Dahiya]
|source_dirs=browser/extensions/screenshots
|components=Firefox::Screenshots, Cloud Services::Server: Screenshots
}}

{{Module
|name=Standalone Composer
|description=Standalone editor/composer based on mozilla/toolkit
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=dev-tech-editor,dev-apps-other
|source_dirs=composer/
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu
|components=
}}

{{Module
|name=URL Classifier
|description=Database and list-based classification of URL resources,
such as Tracking Protection and SafeBrowsing.
|owner=[mailto:francois@mozilla.com François Marier] (client), [mailto:lcrouch@mozilla.com Luke Crouch] (server)
|peers=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client), [mailto:hchang@mozilla.com Henry Chang] (client), [mailto:dlee@mozilla.com Dimi Lee] (client), [mailto:rtilder@mozilla.com Ryan Tilder] (server)
|group=mozilla.dev.platform
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar
|url=
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation
|components=
}}

{{Module
|name=Venkman
|description=JavaScript Debugger frontend
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-apps-js-debugger
|source_dirs=extensions/venkman/
|url=http://www.mozilla.org/projects/venkman
http://www.hacksrus.com/~ginda/venkman/
|components=Other Applications::Venkman JS Debugger
}}

DevTools/Roadmap

2017-09-04T15:00:16Z

Pbrosset: Deleted this obsolete page

DevTools/RoadmapJune2011

2017-09-04T14:58:31Z

Pbrosset: Deleted this obsolete page

DevTools/Roadmap/2011

2017-09-04T14:58:02Z

Pbrosset: Deleted this obsolete page

Modules/Other

2017-07-10T13:56:37Z

Pbrosset: Eddy and jWe talked to Eddy and James, they're not going to contribute to DevTools anymore.

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Add-on SDK
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Myk Melez, Will Bamberg
|forum=http://groups.google.com/group/mozilla-labs-jetpack
|source_dirs=https://github.com/mozilla/addon-sdk
|url=https://wiki.mozilla.org/Jetpack
|components=Add-on SDK
}}

{{Module
|name=Android Background Services
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.
|owner=[mailto:rnewman@mozilla.com Richard Newman]
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox]
|forum=mozilla.dev.platforms.mobile
|source_dirs=https://github.com/mozilla-services/android-sync
|url=https://wiki.mozilla.org/Android/Services
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]
}}

{{Module
|name=BrowserID
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..)
|owner=Ben Adida
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons
|source_dirs=
BrowserID server code: https://github.com/mozilla/browserid,
BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity
|forum=https://lists.mozilla.org/listinfo/dev-identity
}}

{{Module
|name=ChatZilla
|description=IRC client
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]
|group=dev-apps-chatzilla
|source_dirs=extensions/irc/
|url=http://chatzilla.hacksrus.com/
|components=Other Applications::ChatZilla
}}

{{Module
|name=Composer
|description=Editor/Composer
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-tech-editor
|source_dirs=editor/
|url=http://www.mozilla.org/editor
|components=Composer
}}

{{Module
|name=Content Services Infrastructure
|description=A set of data services that allow for content to be served and measured
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]
|peers=[mailto:tspurway@mozilla.com Tim Spurway]
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx
|url=https://wiki.mozilla.org/Tiles
|components=Content Services
}}

{{Module
|name=DevTools
|description=Mozilla Developer Tools
|owner=[mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jwalker@mozilla.com Joe Walker]
|peers=[mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes],[mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:jsantell@mozilla.com Jordan Santell], [mailto:ttromey@mozilla.com Tom Tromey], [mailto:jsnajdr@gmail.com Jaroslav Šnajdr], [mailto:lclark@mozilla.com Lin Clark], [mailto:jlaster@mozilla.com Jason Laster], [mailto:odvarko@gmail.com Jan 'Honza' Odvarko], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:mferretti@mozilla.com Matteo Ferretti], [mailto:chevobbe.nicolas@gmail.com Nicolas Chevobbe], [mailto:ystartsev@mozilla.com Yulia Startsev], [mailto:sole@mozilla.com Soledad Penadés], [mailto:jwajsberg@mozilla.com Julien Wajsberg], [mailto:sfink@mozilla.com Steve Fink] (heapsnapshot code)
|peersemeritus=Mihai Șucan, Rob Campbell, Heather Arthur, Anton Kovalyov, Brandon Benvie, Eddy Bruel, James Long
|group=dev-developer-tools
|source_dirs=devtools
|url=https://wiki.mozilla.org/DevTools
|components=Firefox::Developer Tools
}}

{{Module
|name=Directory SDK
|description=Tools and SDKs for accessing LDAP Directories.
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]
|group=dev-tech-ldap
|source_dirs=directory/
|url=http://www.mozilla.org/directory
|components=Directory
}}

{{Module
|name=DOM Inspector
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=
|source_dirs=extensions/inspector/, layout/inspector/
|url=
|components=Other Applications::DOM Inspector
}}

{{Module
|name=Firefox for Android (Fennec)
|description=Mobile Web Browser
|owner=[mailto:snorp@mozilla.com James Willcox (:snorp)] [mailto:sebastian@mozilla.com Sebastian Kaspari (:sebastian) ]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson (:bnicholson)], [mailto:rnewman@mozilla.com Richard Newman (:rnewman)], [mailto:liuche@mozilla.com Chenxia Liu (:liuche)], [mailto:nalexander@mozilla.com Nick Alexander (:nalexander)], [mailto:mcomella@mozilla.com Michael Comella (:mcomella)], [mailto:ahunt@mozilla.com Andrzej Hunt (:ahunt)], [mailto:gkruglov@mozilla.com Grisha Kruglov (:grisha)]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=mobile/
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for Android
}}

{{Module
|name=Firefox for iOS (Fennec)
|description=Mobile Web Browser
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:sleroux@mozilla.com Steph Leroux], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=https://github.com/mozilla/firefox-ios
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for iOS
}}

{{Module
|name=Firefox Accounts
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.
|owner=[mailto:ckarlof@mozilla.com Chris Karlof]
|peers=[mailto:dcoates@mozilla.com Danny Coates], [mailto:zcarter@mozilla.com Zach Carter], [mailto:rfkelly@mozilla.com Ryan Kelly], [mailto:chilts@mozilla.com Andrew Chilton], [mailto:fmarier@mozilla.com Francois Marier], [mailto:smcarthur@mozilla.com Sean McArthur], [mailto:nchapman@mozilla.com Nick Chapman], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:jrgm@mozilla.com John Morrison], [mailto:pdehaan@mozilla.com Peter deHaan]
|group=
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts
}}

{{Module
|name=Firefox for Metro
|description=Touch-screen-friendly browser for Windows
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]
|forum=https://mail.mozilla.org/listinfo/metro
|source_dirs=browser/metro
|url=https://wiki.mozilla.org/Firefox/Metro
|components=Firefox for Metro
}}

{{Module
|name=Loop aka Firefox Hello
|description=Voice and Video Collaboration System
|owner=[mailto:standard8@mozilla.com Mark Banner]
|peers=[mailto:abr@mozilla.com Adam Roach], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client
|url=https://wiki.mozilla.org/Loop
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop
}}

{{Module
|name=Mozilla Location Service (MLS)
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]
|peers=
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/ichnaea
|url=https://location.services.mozilla.com
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues
}}

{{Module
|name=Mozilla Stumbler ("MozStumbler")
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).
|owner=Garvan Keeley
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/MozStumbler
|url=https://location.services.mozilla.com
|components=https://github.com/mozilla/MozStumbler/issues
}}

{{Module
|name=Sync
|description=Firefox Sync client
|owner=[mailto:mconnor@mozilla.com Mike Connor]
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen
|group=
|source_dirs=services/sync/
|url=https://wiki.mozilla.org/Services/Process/Code_Review
|components=Sync
}}

{{Module
|name=Party Tool
|description=PHP-based party tool used for Firefox Party
|owner=[mailto:rflint@ryanflint.com Ryan Flint]
|peers=Mike Morgan, [mailto:reed@reedloden.com Reed Loden]
|group=dev-apps-webtools
|source_dirs=webtools/partytool/
|url=http://wiki.mozilla.org/Webtools:PartyTool
|components=
}}

{{Module
|name=Penelope
|description=Eudora-like functionality and theme added to Thunderbird.
|owner=Jeff Beckley
|peers=
|group=
|source_dirs=penelope/
|url=https://wiki.mozilla.org/Penelope
|components=Penelope
}}

{{Module
|name=Popcorn.js
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/popcorn-js/
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview
}}

{{Module
|name=Popcorn Maker
|description=An SDK for authoring Popcorn projects.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/butter/
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview
}}

{{Module
|name=Rhino
|description=JavaScript interpreter/compiler implemented in Java
|owner=[mailto:greg@apigee.com Greg Brail]
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]
|group=dev-tech-js-engine
|source_dirs=js/rhino/
|url=http://www.mozilla.org/rhino/
|components=Rhino
}}

{{Module
|name=Standalone Composer
|description=Standalone editor/composer based on mozilla/toolkit
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=dev-tech-editor,dev-apps-other
|source_dirs=composer/
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu
|components=
}}

{{Module
|name=URL Classifier
|description=Database and list-based classification of URL resources,
such as Tracking Protection and SafeBrowsing.
|owner=[mailto:francois@mozilla.com François Marier] (client), [mailto:lcrouch@mozilla.com Luke Crouch] (server)
|peers=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client), [mailto:hchang@mozilla.com Henry Chang] (client), [mailto:dlee@mozilla.com Dimi Lee] (client), [mailto:rtilder@mozilla.com Ryan Tilder] (server)
|group=mozilla.dev.platform
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar
|url=
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation
|components=
}}

{{Module
|name=Venkman
|description=JavaScript Debugger frontend
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-apps-js-debugger
|source_dirs=extensions/venkman/
|url=http://www.mozilla.org/projects/venkman
http://www.hacksrus.com/~ginda/venkman/
|components=Other Applications::Venkman JS Debugger
}}

QA/DevTools Go Faster

2017-07-04T12:56:47Z

Pbrosset: Changed title

'''Approvals Required / Received'''

The following individuals are required to/have approved this Test Plan:

{| class="wikitable"
|-
! Name !! Title !! Department !! Approval Date !! Method
|-
| Cornel Ionce || QA Manager || Product Integrity || Date || [mailto:cornel.ionce@softvisioninc.eu Email]
|-
| Patrick Brosset || Engineering Manager || Engineering || Date || [mailto:pbrosset@mozilla.com Email]
|-
| Bryan Clark || EPM || Product Management || Date || [mailto:bclark@mozilla.com Email]
|}

'''Revision History'''

This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded). The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.

{| class="wikitable" style="width:60%"
|-
! Date !! Version !! Author !! Description
|-
| 05/22/2017 || 1.0 || Iulia Cristescu || Created first draft
|-
| 06/20/2017 || 2.0 || Iulia Cristescu || Updated most of the sections
|-
| 06/23/2017 || 3.0 || Iulia Cristescu || Updated Approvals, Risk Assessment and Coverage, Test Areas and Sign Off Criteria sections
|-
|}

= Overview =
== Purpose ==
DevTools Go Faster is about shipping DevTools as an on-demand add-on to the Firefox users. 99% of Firefox users don't use DevTools and for the users who do the 90% of them are on the Release channel. Converting DevTools to an add-on allows removing DevTools from most Firefox installs and ship DevTools to the developers faster than ever.

== Scope ==
This wiki details the testing that will be performed by the project team for the DevTools Go Faster project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
* What will be tested
* How testing will be performed

== Ownership ==

'''Stakeholders'''
* Product Manager - [mailto:bclark@mozilla.com Bryan Clark]
* Overall Product - Jeff Griffiths
'''Engineering'''
* Engineering Manager - [mailto:pbrosset@mozilla.com Patrick Brosset]
* Overall Engineer - Joe Walker
* Engineering - [mailto:ochameau@mozilla.com Alexandre Poirot]
* Engineering - [mailto:odvarko@gmail.com Honza]
* Engineering - [mailto:jdescottes@mozilla.com Julian Descottes]
'''QA'''
* QA Manager - [mailto:cornel.ionce@softvisioninc.eu Cornel Ionce]
* PM for QA team - [mailto:fmezei@mozilla.com Florin Mezei]
* TL for QA team - [mailto:avaida@mozilla.com Andrei Vaida]
* Leading QA efforts - [mailto:icristescu@mozilla.com Iulia Cristescu]
* Leading QA efforts (peer) - [mailto:asimonca@mozilla.com Alexandru Simonca]

= Testing summary =

== Scope of Testing ==
=== In Scope ===
DevTools lets you examine, edit, and debug HTML, CSS, and JavaScript on the desktop and on mobile. 
DevTools will become a Mozilla extension that can be installed on demand by the user (using an UI that detects when someone needs DevTools) and will be updated outside of the Firefox's release cycle. 
For existing Firefox DevTools users there should be no noticeable change in their daily experience. 
'''DevTools Shim''' is responsible for installing the DevTools add-on as needed. The Shim will auto-install the add-on for existing DevTools users by default. The Shim is listening to the DevTools keyboard shortcuts and provides install methods at other various entry points like about:debugging. When new users use a DevTools keyboard shortcut Firefox will prompt them, asking if they want to install DevTools. If the the answer is yes, the DevTools add-on will be installed and will update itself in the background from that point on. 
The testing efforts will be invested on the following areas:
* previous usage detection;
* add-on installation work flow and its integration with the current browser functionalities and UI;
* DevTools basic and advanced functionality and usability, according to the existing requirements.

=== Out of Scope ===
* The mobile implementation and testing are not targeted
* Storage inspector, StyleEditor, Canvas Debugger, Shader Editor, Performance, Memory, Settings are not covered

= Requirements for testing =
== Environments ==
Testing will be performed across platform (both x86 & x64 infrastructures), targeting:
* Windows 10
* Windows 7
* Ubuntu 16.04
* macOS 10.12

= Test Strategy =
== Risk Assessment and Coverage ==

{| class="wikitable"
|-
! ID !! Description / Threat Description !! Covered by Test Objective !! Magnitude !! Probability !! Priority !! Impact Score
|-
| 1 || Compatibility across all available channels || Testing should cover all the Firefox channels (from Release to Nightly) || 2-Moderate || 2-Possible || 3-High || 4
|-
| 2 || Differences depending on channels (built in vs. add-on) and profiles (already opened DevTools vs. never opened DevTools) || Testing should also regard the previous usage detection process and the differences induced by the installation work flow || 3-High || 3-Almost Certain || 3-High || 12
|-
| 3 || Localization/RTL || Testsuite will include RTL/non-RTL differentiation || 2-Moderate || 2-Possible || 3-High || 12
|-
| 4 || Accessibility/e10s || Testsuite will include e10s/non-e10s differentiation || 2-Moderate || 2-Possible || 3-High || 12
|-
| 5 || Platform specific issues || Most users are using Windows but the team mostly works on OSX/Unix, so there is a risk for Windows only regressions. Therefore the testing process will assure full platform coverage || 3-High || 3-Almost Certain || 3-High || 12
|}

'''Values:'''

* '''Magnitude:''' 1- Low , ''2-Moderate'', '''3-High'''

* '''Probability:''' 1-Unlikely, ''2-Possible'', '''3-Almost Certain'''

* '''Priority:''' 1 - Low, ''2-Medium'', '''3-High'''

'''Impact Score Breakdown:'''
* An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
* An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
* An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.

== Test Objectives ==
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master.
This could be documented in bullet form or in a table similar to the one below.

{| class="wikitable"
|-
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners
|-
| 1 || Previous usage detection || Verify if DevTools previous usage state is properly detected on Beta and Release builds and if the corresponding install process is initiated || If DevTools was previously used, the addon is automatically downloaded and installed. If the user never tried DevTools, it will go through the install process || Manual || Release QA
|-
| 2 || Install entry points || Verify if the entry points for users to install DevTools are captured || The corresponding install work flow is initiated when DevTools are launched, depending on the previous usage status || Manual || Release QA
|-
| 3 || Install work flow || Verify if the installation process is properly executed || Depending on the captured entry point, the corresponding install page is opened in a new tab and the installation process is successfully completed || Manual || Release QA
|-
| 4 || DevTools functionality and usability || Verify if all DevTools functionalities are working || Toolbox, Inspector, Console, Debugger, Netmonitor and all the related tools are fully functional and no regressions are triggered by the new install work flow || Manual || Release QA
|}

== Builds ==
DevTools Go Faster will be tested on the following builds:
* Nightly - starting with the build from
* DevEdition - starting with the build from
* Beta - starting with
* Release - starting with

== Test Execution Schedule ==
The following table identifies the anticipated testing period available for test execution.
{| class="wikitable" style="width:60%"
|-
! Project phase !! Start Date !! End Date
|-
| Start project
|style="text-align:center;" | 05/01/2017 ||
|-
| Study documentation/specs received from developers
|style="text-align:center;" | 05/20/2017 ||
|-
| QA - Test plan creation
|style="text-align:center;" | 05/22/2017 ||
|-
| QA - Test cases/Env preparation
|style="text-align:center;" | 06/06/2017 ||
|-
| QA - Nightly Testing
|style="text-align:center;" | ||
|-
| QA - Beta Testing
|style="text-align:center;" | ||
|-
| Release Date
|style="text-align:center;" | ||
|}

== Testing Tools ==
Detail the tools to be used for testing, for example see the following table:
{| class="wikitable" style="width:50%"
|-
! Process !! Tool
|-
| Test plan creation || Mozilla wiki
|-
| Test case creation || TestRail
|-
| Test case execution || TestRail
|-
| Bugs management || GitHub & Bugzilla
|}

= Status =
== Overview ==
* Released to Nightly starting with
* Merged to beta starting with
* Merged to Release starting with

= References =
List and links for specs:
* [https://public.etherpad-mozilla.org/p/DevTools_Go_Faster_QA_kick_off Etherpad for DevTools_Go_Faster_QA_kick_off]
* [https://trello.com/c/ctmEsEVa/237-go-faster-devtools-outside-fx-releases-as-an-add-on Trello]
* [https://docs.google.com/document/d/1_cl1ZtcS7zFy4JTmh4ShqaVl0HHnXrN2oHBcJMgN6lU/edit#heading=h.kft9zibe60g5 General spec]
* [https://docs.google.com/document/d/1tod1YH8uuzZykKawNvrLyyxuxxYNUfYsvTuHFa2Jf9s/edit#heading=h.98oflqxiqqz8 FAQ]
* [https://docs.google.com/document/d/1CqBkNR2XWaItZnotb2cYJXooOH2k5LpVljx9yTjH96Q/edit#heading=h.tfjwr92eubne Moving DevTools to github]
* [https://docs.google.com/document/d/1zhVL4bROBk7Q5T_GhEERnWqtAZT2zTxSWj1ymU4Z_9o/edit#heading=h.mgyxetq9yvfk Tracking internal feedback about DevTools GoFaster]
* [https://docs.google.com/document/d/1ku6Jn12XdTFNno0phhLjlBD2H43k5NYswALYnA_UVBA/edit# Firefox Shim]

= Testcases =
== Test Areas ==
{| class="wikitable" style="width:80%"
|-
! Test Areas !! Covered !! Details
|-
| Private Window
|style="text-align:center;" | Yes ||
|-
| Multi-Process Enabled
|style="text-align:center;" | Yes ||
|-
| Multi-process Disabled
|style="text-align:center;" | Yes ||
|-
| Theme (high contrast)
|style="text-align:center;" | No ||
|-
| '''UI'''
|| ||
|-
| Mouse-only operation
|style="text-align:center;" | Yes ||
|-
| Keyboard-only operation
|style="text-align:center;" | Yes ||
|-
| Display (HiDPI)
|style="text-align:center;" | No ||
|-
| Interaction (scroll, zoom)
|style="text-align:center;" | Yes ||
|-
| Usable with a screen reader
|style="text-align:center;" | No || e.g. with NVDA
|-
| Usability and/or discoverability testing
|style="text-align:center;" | Yes || Is this feature user friendly
|-
| RTL build testing
|style="text-align:center;" | Yes ||
|-
| '''Help/Support'''
|| ||
|-
| Help/support interface required
|style="text-align:center;" | Yes || Make sure link to support/help page exist and is easy reachable.
|-
| Support documents planned(written)
|style="text-align:center;" | Yes || Make sure support documents are written and are correct.

|-
| '''Install/Upgrade'''
|| ||
|-
| Feature upgrades/downgrades data as expected
|style="text-align:center;" | Yes ||
|-
| Does sync work across upgrades
|style="text-align:center;" | No ||
|-
| Requires install testing
|style="text-align:center;" | Yes || separate feature/application installation needed (not only Firefox)
|-
| Affects first-run or onboarding
|style="text-align:center;" | Yes || Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned.
|-
| Does this affect partner builds? Partner build testing
|style="text-align:center;" | No || yes/no options, add comment with details about who will lead testing

|-
| ''' Enterprise '''
|| || Raise up the topic to developers to see if they are expecting to work different on ESR builds
|-
| Enterprise administration
|style="text-align:center;" | No ||
|-
| Network proxies/autoconfig
|style="text-align:center;" | No ||
|-
| ESR behavior changes
|style="text-align:center;" | No ||
|-
| Locked preferences
|style="text-align:center;" | No ||

|-
| ''' Data Monitoring '''
|| ||
|-
| Temporary or permanent telemetry monitoring
|style="text-align:center;" | No || List of error conditions to monitor
|-
| Telemetry correctness testing
|style="text-align:center;" | No ||
|-
| Server integration testing
|style="text-align:center;" | No ||
|-
| Offline and server failure testing
|style="text-align:center;" | No ||
|-
| Load testing
|style="text-align:center;" | No ||

|-
| ''' Add-ons '''
|| || If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on.
|-
| Addon API required?
|style="text-align:center;" | No ||
|-
| Comprehensive API testing
|style="text-align:center;" | No ||
|-
| Permissions
|style="text-align:center;" | No ||
|-
| Testing with existing/popular addons
|style="text-align:center;" | No ||

|-
| ''' Security '''
|| || Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature.
|-
| 3rd-party security review
|style="text-align:center;" | No ||
|-
| Privilege escalation testing
|style="text-align:center;" | No ||
|-
| Fuzzing
|style="text-align:center;" | No ||

|-
| ''' Web Compatibility '''
|| || depends on the feature
|-
| Testing against target sites
|style="text-align:center;" | Yes ||
|-
| Survey of many sites for compatibility
|style="text-align:center;" | Yes ||

|-
| ''' Interoperability '''
|| || depends on the feature
|-
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers.
|style="text-align:center;" | No ||
|-
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS
|style="text-align:center;" | No ||
|-
| Interaction of this feature with other browser features
|style="text-align:center;" | Yes ||
|}

== Test suite ==
Full Test suite - [https://testrail.stage.mozaws.net/index.php?/suites/view/1111&group_by=cases:section_id&group_order=asc Testrail]
Smoke Test suite - [https://testrail.stage.mozaws.net/index.php?/suites/view/1111&group_by=cases:section_id&group_id=4053&group_order=asc Testrail]
Regression Test suite - Link with the tests - if available/needed

= Bug Work =
'''Reference bugs'''
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1361080 1361080 - Create a UI shim to install/bootstrap devtools addon]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1373492 1373492 - Enable the layout view]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1347964 1347964 - |meta| Ship the new Inspector Layout panel]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1363533 1363533 - Setup a build configuration to build firefox without built-in DevTools]

= Sign off =
== Criteria ==
Checklist
* All test cases should be executed
* Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)

== Results ==
'''Nightly testing''' 

List of OSes that will be covered by testing 
*Link for the tests run
** Full Test suite, link to TestRail - Tests Runs and Results [https://testrail.stage.mozaws.net/index.php?/runs/overview/17 link]
** Daily Smoke, if needed/available
** Regression Test suite, if needed/available
 

'''Merge to Beta Sign-off''' 
List of OSes that will be covered by testing 
*Link for the tests run
** Full Test suite

== Checklist ==
{| class="wikitable" style="width:60%"
|-
! Exit Criteria !! Status !! Notes/Details
|-
| Testing Prerequisites (specs, use cases)
| style="text-align:center;" |
| style="text-align:center;" |
|-
| Testing Infrastructure setup
|style="text-align:center;" | ||
|-
| Test Plan Creation
| style="text-align:center;" | ||
|-
| Test Cases Creation
|style="text-align:center;" | ||
|-
| Automation Coverage ||
|style="text-align:center;" |
|-
| Performance Testing
|style="text-align:center;" | ||
|-
| All Defects Logged || ||
|-
| Critical/Blockers Fixed and Verified || ||
|-
| Metrics/Telemetry||
|style="text-align:center;" |
|-
| Basic/Core functionality Nightly testing
|style="text-align:center;" |
|style="text-align:center;" |
|-
| QA mid-Nightly Signoff||
|style="text-align:center;" | Email to be sent
|-
| QA Nightly - Full Testing
|style="text-align:center;" | ||
|-
| QA pre-Beta Signoff||
|style="text-align:center;"| Email to be sent
|-
| QA Beta - Full Testing
|style="text-align:center;" | ||
|-
| QA pre-Release Signoff ||
|style="text-align:center;" | Email to be sent
|}

Modules/Other

2017-07-04T12:32:36Z

Pbrosset: Adding 3 peers to the DevTools module (Yulia, Sole and Julien). Sent an email to the governance mailing list.

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Add-on SDK
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Myk Melez, Will Bamberg
|forum=http://groups.google.com/group/mozilla-labs-jetpack
|source_dirs=https://github.com/mozilla/addon-sdk
|url=https://wiki.mozilla.org/Jetpack
|components=Add-on SDK
}}

{{Module
|name=Android Background Services
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.
|owner=[mailto:rnewman@mozilla.com Richard Newman]
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox]
|forum=mozilla.dev.platforms.mobile
|source_dirs=https://github.com/mozilla-services/android-sync
|url=https://wiki.mozilla.org/Android/Services
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]
}}

{{Module
|name=BrowserID
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..)
|owner=Ben Adida
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons
|source_dirs=
BrowserID server code: https://github.com/mozilla/browserid,
BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity
|forum=https://lists.mozilla.org/listinfo/dev-identity
}}

{{Module
|name=ChatZilla
|description=IRC client
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]
|group=dev-apps-chatzilla
|source_dirs=extensions/irc/
|url=http://chatzilla.hacksrus.com/
|components=Other Applications::ChatZilla
}}

{{Module
|name=Composer
|description=Editor/Composer
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-tech-editor
|source_dirs=editor/
|url=http://www.mozilla.org/editor
|components=Composer
}}

{{Module
|name=Content Services Infrastructure
|description=A set of data services that allow for content to be served and measured
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]
|peers=[mailto:tspurway@mozilla.com Tim Spurway]
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx
|url=https://wiki.mozilla.org/Tiles
|components=Content Services
}}

{{Module
|name=DevTools
|description=Mozilla Developer Tools
|owner=[mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jwalker@mozilla.com Joe Walker]
|peers=[mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes],[mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:ejpbruel@mozilla.com Eddy Bruel], [mailto:jlongster@mozilla.com James Long], [mailto:jsantell@mozilla.com Jordan Santell], [mailto:ttromey@mozilla.com Tom Tromey], [mailto:jsnajdr@gmail.com Jaroslav Šnajdr], [mailto:lclark@mozilla.com Lin Clark], [mailto:jlaster@mozilla.com Jason Laster], [mailto:odvarko@gmail.com Jan 'Honza' Odvarko], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:mferretti@mozilla.com Matteo Ferretti], [mailto:chevobbe.nicolas@gmail.com Nicolas Chevobbe], [mailto:ystartsev@mozilla.com Yulia Startsev], [mailto:sole@mozilla.com Soledad Penadés], [mailto:jwajsberg@mozilla.com Julien Wajsberg], [mailto:sfink@mozilla.com Steve Fink] (heapsnapshot code)
|peersemeritus=Mihai Șucan, Rob Campbell, Heather Arthur, Anton Kovalyov, Brandon Benvie
|group=dev-developer-tools
|source_dirs=devtools
|url=https://wiki.mozilla.org/DevTools
|components=Firefox::Developer Tools
}}

{{Module
|name=Directory SDK
|description=Tools and SDKs for accessing LDAP Directories.
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]
|group=dev-tech-ldap
|source_dirs=directory/
|url=http://www.mozilla.org/directory
|components=Directory
}}

{{Module
|name=DOM Inspector
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=
|source_dirs=extensions/inspector/, layout/inspector/
|url=
|components=Other Applications::DOM Inspector
}}

{{Module
|name=Firefox for Android (Fennec)
|description=Mobile Web Browser
|owner=[mailto:snorp@mozilla.com James Willcox (:snorp)] [mailto:sebastian@mozilla.com Sebastian Kaspari (:sebastian) ]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson (:bnicholson)], [mailto:rnewman@mozilla.com Richard Newman (:rnewman)], [mailto:liuche@mozilla.com Chenxia Liu (:liuche)], [mailto:nalexander@mozilla.com Nick Alexander (:nalexander)], [mailto:mcomella@mozilla.com Michael Comella (:mcomella)], [mailto:ahunt@mozilla.com Andrzej Hunt (:ahunt)], [mailto:gkruglov@mozilla.com Grisha Kruglov (:grisha)]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=mobile/
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for Android
}}

{{Module
|name=Firefox for iOS (Fennec)
|description=Mobile Web Browser
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:sleroux@mozilla.com Steph Leroux], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=https://github.com/mozilla/firefox-ios
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for iOS
}}

{{Module
|name=Firefox Accounts
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.
|owner=[mailto:ckarlof@mozilla.com Chris Karlof]
|peers=[mailto:dcoates@mozilla.com Danny Coates], [mailto:zcarter@mozilla.com Zach Carter], [mailto:rfkelly@mozilla.com Ryan Kelly], [mailto:chilts@mozilla.com Andrew Chilton], [mailto:fmarier@mozilla.com Francois Marier], [mailto:smcarthur@mozilla.com Sean McArthur], [mailto:nchapman@mozilla.com Nick Chapman], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:jrgm@mozilla.com John Morrison], [mailto:pdehaan@mozilla.com Peter deHaan]
|group=
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts
}}

{{Module
|name=Firefox for Metro
|description=Touch-screen-friendly browser for Windows
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]
|forum=https://mail.mozilla.org/listinfo/metro
|source_dirs=browser/metro
|url=https://wiki.mozilla.org/Firefox/Metro
|components=Firefox for Metro
}}

{{Module
|name=Loop aka Firefox Hello
|description=Voice and Video Collaboration System
|owner=[mailto:standard8@mozilla.com Mark Banner]
|peers=[mailto:abr@mozilla.com Adam Roach], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client
|url=https://wiki.mozilla.org/Loop
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop
}}

{{Module
|name=Mozilla Location Service (MLS)
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]
|peers=
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/ichnaea
|url=https://location.services.mozilla.com
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues
}}

{{Module
|name=Mozilla Stumbler ("MozStumbler")
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).
|owner=Garvan Keeley
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/MozStumbler
|url=https://location.services.mozilla.com
|components=https://github.com/mozilla/MozStumbler/issues
}}

{{Module
|name=Sync
|description=Firefox Sync client
|owner=[mailto:mconnor@mozilla.com Mike Connor]
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen
|group=
|source_dirs=services/sync/
|url=https://wiki.mozilla.org/Services/Process/Code_Review
|components=Sync
}}

{{Module
|name=Party Tool
|description=PHP-based party tool used for Firefox Party
|owner=[mailto:rflint@ryanflint.com Ryan Flint]
|peers=Mike Morgan, [mailto:reed@reedloden.com Reed Loden]
|group=dev-apps-webtools
|source_dirs=webtools/partytool/
|url=http://wiki.mozilla.org/Webtools:PartyTool
|components=
}}

{{Module
|name=Penelope
|description=Eudora-like functionality and theme added to Thunderbird.
|owner=Jeff Beckley
|peers=
|group=
|source_dirs=penelope/
|url=https://wiki.mozilla.org/Penelope
|components=Penelope
}}

{{Module
|name=Popcorn.js
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/popcorn-js/
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview
}}

{{Module
|name=Popcorn Maker
|description=An SDK for authoring Popcorn projects.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/butter/
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview
}}

{{Module
|name=Rhino
|description=JavaScript interpreter/compiler implemented in Java
|owner=[mailto:greg@apigee.com Greg Brail]
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]
|group=dev-tech-js-engine
|source_dirs=js/rhino/
|url=http://www.mozilla.org/rhino/
|components=Rhino
}}

{{Module
|name=Standalone Composer
|description=Standalone editor/composer based on mozilla/toolkit
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=dev-tech-editor,dev-apps-other
|source_dirs=composer/
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu
|components=
}}

{{Module
|name=URL Classifier
|description=Database and list-based classification of URL resources,
such as Tracking Protection and SafeBrowsing.
|owner=[mailto:francois@mozilla.com François Marier] (client), [mailto:lcrouch@mozilla.com Luke Crouch] (server)
|peers=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client), [mailto:hchang@mozilla.com Henry Chang] (client), [mailto:dlee@mozilla.com Dimi Lee] (client), [mailto:rtilder@mozilla.com Ryan Tilder] (server)
|group=mozilla.dev.platform
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar
|url=
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation
|components=
}}

{{Module
|name=Venkman
|description=JavaScript Debugger frontend
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-apps-js-debugger
|source_dirs=extensions/venkman/
|url=http://www.mozilla.org/projects/venkman
http://www.hacksrus.com/~ginda/venkman/
|components=Other Applications::Venkman JS Debugger
}}

DevTools

2017-05-03T16:35:20Z

Pbrosset: Moved debugger client API to the tree, no need for it to be linked from here anymore.

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

Read [https://devtools-html.github.io/#getting-in-touch this page] for more information about talking with the team, filing bugs, or even fixing a bug yourself!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

DevTools technical docs are available in the DevTools source code under the <code>/devtools/docs</code> directory.
You can read them online here: http://searchfox.org/mozilla-central/source/devtools/docs/SUMMARY.md

Some technical docs are still in the process of being moved to this location, but are available here on the wiki in the meantime:

* [[Debugger Architecture]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

Debugger Client API

2017-05-03T16:34:27Z

Pbrosset: Moved to the tree

This doc was moved to http://searchfox.org/mozilla-central/source/devtools/docs/backend/client-api.md

DevTools/Hacking

2017-04-07T18:47:33Z

Pbrosset: Moved RDP doc to the tree

Want to work on [[DevTools|Firefox Developer Tools]]? You've come to the right place! If you want more information about contributing, check out our guide for [[DevTools/GetInvolved|getting involved]].

= Building, running, updating and rebuilding =

== First Build ==

Follow the instructions on [https://developer.mozilla.org/En/Simple_Firefox_build how to build Firefox]. Roughly:

hg clone http://hg.mozilla.org/mozilla-central
./mach build

For your first build, this should do the trick. If you are going to be building a lot, you may want to set up your [https://developer.mozilla.org/en-US/docs/Configuring_Build_Options .mozconfig file].

== First Run ==

Once you have built Firefox, you can run it with

$ ./mach run

or

$ ./mach run -P development

What is the <code>-P development</code>? It is a flag telling Firefox to use a different [https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data profile], named "development" (this name can be anything you want). If it does not exist the first time you run it, Firefox will open a popup and you can create a new profile with the name you passed in. If you don't specify a profile, <code>mach</code> will create a temporary profile in the path <code><objdir>/tmp/scratch_user</code>.

Once this command runs, you should see a new Firefox window, called "Nightly".

== Incremental Builds ==

Once you've already built Firefox once, if you want to update with the latest changes from the repo, run:

$ hg pull -u

To build with the latest changes or with your own DevTools changes, you can run:

$ ./mach build faster

which is much faster than your first build or clobber builds and should only take a few seconds. You can run your build the same way you did before:

$ ./mach run -P development

If you happen to change any C++ files (which is pretty rare when working on DevTools), you may need a different command for incremental builds:

$ ./mach build binaries

A full <code>./mach build</code> will work for any type of change, it just takes longer to run than the incremental options above.

Note that whenever you pull the latest changes from <tt>fx-team</tt> into your local repository, you may need to "clobber". A "clobber" is similar to a "<code>make clean</code>". You'll know you need to clobber when you get a big error message telling you to do a clobber build after you tried to do an incremental build. To do a clobber build, enter these commands:

$ ./mach clobber
$ ./mach build

== Artifact builds (or: building faster!) ==

If you are '''not''' going to modify any C/C++ code, you could use artifact builds. This method downloads prebuilt components, and then the build process becomes faster.

Essentially, add the following lines to your .mozconfig file:

# Automatically download and use compiled C++ components:
ac_add_options --enable-artifact-builds

# Write build artifacts to:
mk_add_options MOZ_OBJDIR=./objdir-frontend

And then you can follow the normal build process.

On OSX you might want to use <tt>MOZ_OBJDIR=./objdir-frontend.noindex</tt> instead. Using the .noindex file extension prevents spotlight from indexing your objdir, which is slow.

For more information on aspects such as technical limitations, read the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds Artifact Builds] page.

= Configuring your dev profile =

You will want to make a couple of quick changes to the profile you use when running your version of Firefox.

== Enable remote debugging and the Browser Toolbox ==

Open DevTools, and click the "Toolbox Options" gear icon in the top right (the image underneath is outdated). Make sure the following two options are checked:

* '''Enable browser chrome and add-on debugging toolboxes'''
* '''Enable remote debugging'''

These settings allow you to use the [https://developer.mozilla.org/docs/Tools/Browser_Toolbox browser toolbox] to set breakpoints inside of the DevTools code, inspect the DevTools themselves, and let you run the [https://developer.mozilla.org/en-US/docs/Tools/Scratchpad Scratchpad] in the ''Browser'' environment.

[[Image:DevToolsDeveloperSettings.png|center|600px|Settings for developer tools - "Enable Chrome Debugging" and "Enable Remote Debugging"]]

You might also want to change the following preference in '''<tt>about:config</tt>''' to <code>false</code>:

* '''devtools.debugger.prompt-connection'''

This will get rid of the prompt displayed every time you open the browser toolbox.

== Enabling DevTools Logging ==

Depending on what you are working on, you may want to make some changes to your profile to enable more logging. If you type '''<tt>about:config</tt>''' in the URL bar, click through the warning page, and search for '''<tt>devtools</tt>''' you can see some of them.

Add the global "dump" function to all windows which logs strings to stdout.

'''browser.dom.window.dump.enabled''' = true

Dumps all packets sent over the remote debugging protocol to stdout (requires browser.dom.window.dump.enabled):

'''devtools.debugger.log''' = true

Log every event notification from the EventEmitter class (devtools/shared/event-emitter.js) (requires browser.dom.window.dump.enabled)

'''devtools.dump.emit''' = true

Restart the browser to apply configuration changes.

You may also be interested in the remote protocol inspector add-on: https://github.com/firebug/rdp-inspector/wiki

== Enabling DevTools Assertions ==

Highly recommended for DevTools hackers!

Add this to your '''<tt>.mozconfig</tt>''':

ac_add_options --enable-debug-js-modules

Assert your own invariants like this:

const { assert } = require("devtools/shared/DevToolsUtils");
// ...
assert(1 + 1 === 2, "I really hope this is true...");

When assertions are enabled, assertion failures are fatal, log console warnings, and throw errors.

When assertions are not enabled, the <tt>assert</tt> function is a no-op.

It also enables the "debug" builds of certain third party libraries, such as React.

= Developer Tools Directories Overview =

* '''<tt>devtools/shared</tt>''': Code shared by both the DevTools client (front-end UI) and server. If we are using any third party libraries, or importing external repositories into our tree, those libraries generally live here (eg, <tt>devtools/shared/acorn</tt>), assuming they are used by both client and server.
** '''<tt>devtools/shared/client</tt>''': Code for the DevTools [Remote Debugging Protocol http://searchfox.org/mozilla-central/source/devtools/docs/backend/protocol.md] client. (You may wonder why this is not in <tt>devtools/client</tt> below: it's mainly because tests in server also need access to the RDP client.)
** '''<tt>devtools/shared/locales</tt>''': Strings used in either the DevTools server only, or shared with both the client and server
* '''<tt>devtools/server</tt>''': Code for the DevTools [Remote Debugging Protocol http://searchfox.org/mozilla-central/source/devtools/docs/backend/protocol.md] server and transport layer.
** '''<tt>devtools/server/actors</tt>''': [[Remote_Debugging_Protocol#Actors RDP Actors]]. Note that if you're modifying the RDP, you may need to worry about [[DevTools/Backwards_Compatibility|backwards compatibilty with older protocol implementations]].
* '''<tt>devtools/client</tt>''': Front end user interfaces for our tools. Should be pretty obvious what is what based on the directory names and each panel we have in our toolbox. This directory is only shipped with desktop Firefox, as opposed to other directories above, which are shipped with all Gecko products (Firefox OS, Firefox for Android, etc.)
** '''<tt>devtools/client/locales</tt>''': Strings used in the DevTools client (front-end UI)
** '''<tt>devtools/client/themes</tt>''': CSS and images used in the DevTools client (front-end UI)

= DevTools Automated Tests =

We use three suites of tests:

* '''xpcshell''': Unit-test style of tests. No browser window, just a JavaScript shell. Mostly testing APIs directly.
* '''mochitest-chrome''': Unit-test style of tests, but with a browser window. Mostly testing APIs that interact with the DOM directly.
* '''mochitest-devtools''': Integration style of tests. Fires up a whole browser window with every test and you can test clicking on buttons, etc.

More information about the different types of tests can be found on the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing MDN automated testing page]

== Running DevTools Tests ==

To run all DevTools tests, regardless of suite type:

$ ./mach test devtools/*

The following sections show more specific commands for running only a single suite or single test in a suite.

=== xpcshell Tests ===

To run all of the xpcshell tests:

$ ./mach xpcshell-test --tag devtools

To run a specific xpcshell test:

$ ./mach xpcshell-test devtools/path/to/the/test_you_want_to_run.js

=== Chrome Mochitests ===

To run the whole suite of chrome mochitests for DevTools:

$ ./mach mochitest -f chrome --tag devtools

To run a specific chrome mochitest:

$ ./mach mochitest devtools/path/to/the/test_you_want_to_run.html

=== DevTools Mochitests ===

To run the whole suite of browser mochitests for DevTools (sit back and relax):

$ ./mach mochitest --subsuite devtools --tag devtools

To run a specific tool's suite of browser mochitests:

$ ./mach mochitest devtools/client/<tool>

For example, run all of the debugger browser mochitests:

$ ./mach mochitest devtools/client/debugger

To run a specific DevTools mochitest:

$ ./mach mochitest devtools/client/path/to/the/test_you_want_to_run.js

Note that the mochitests '''must''' have focus while running.

== Writing Tests ==

When working on a patch for DevTools, there's almost never a reason not to add a new test. If you are fixing a bug, you probably should write a new test to prevent this bug from occurring again. If you're implementing a new feature, you probably should write many new tests to cover the various aspects of this new feature.

You should ask yourself:
* Are there enough tests for my patch?
* Are they the right types of tests?

To help with writing nice, maintainable and consistent DevTools mochitests, please follow our [https://wiki.mozilla.org/DevTools/mochitests_coding_standards DevTools mochitests coding guide].

== Debugging Intermittent Test Failures ==

When a test fails sometimes, but not always, it is called an "intermittent". Handling these is complicated enough that we have a [[DevTools/Intermittents|separate page]] with tips on debugging.

= Finding documentation =

If you read through the source code about something you do not know about, you may find documentation here:

* [http://developer.mozilla.org/ Mozilla Developer Network] has a ton of info about XUL elements, HTML, JS, DOM, Web APIs, Gecko-specific APIs, and more.
* [http://dxr.mozilla.org/mozilla-central/source/ DXR] is a source code search engine - search for symbols you want to learn about, eg. nsIDocument.
* There's some technical [https://dxr.mozilla.org/mozilla-central/source/devtools/docs DevTools documentation in the repository] that you should check.
* And other technical documents on [[DevTools#Internal_Technical_Documentation|on this wiki]]

We recommend [https://support.mozilla.org/en-US/kb/how-search-from-address-bar adding a smart keyword search] for DXR and MDN.
If you still have questions, [[DevTools/GetInvolved#Communication|ask us on IRC]] or leave a comment on the Bugzilla ticket.

= Making and Submitting a Patch =

Before you make any changes, read [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html the documentation on how to use Mozilla's version control].

Before you submit a patch, you should read our [[DevTools/CodingStandards|Coding Standards]] and run [https://wiki.mozilla.org/DevTools/CodingStandards#JS_linting_with_ESLint ESLint] to validate your code changes (to avoid loosing time during code reviews with formatting details for instance). In general, try to be File Consistent. For new files, follow the standards.

Once you have a patch file, add it as an attachment to the Bugzilla ticket you are working on and add the '''feedback?''' or '''review?''' flag depending on if you just want feedback and confirmation you're doing the right thing or if you think the patch is ready to land respectively. Read more about [https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch how to submit a patch and the Bugzilla review cycle here].

You can also take a look at the [[DevTools/Code Review Checklist]] as it contains a list of checks that your reviewer is likely to go over when reviewing your code.

= Coding Standards =

DevTools has some coding standards that your changes should follow:

* [[DevTools/CodingStandards|JavaScript coding standards]]
* [[DevTools/CSSTips|CSS tips]]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/SVG_Guidelines SVG Best practices] and [https://dxr.mozilla.org/mozilla-central/source/devtools/docs/svgs.md guidelines for creating new DevTools SVGs]

= Potential Pitfalls =

Today there are a few techniques and conventions we use that can be confusing, especially when you first start working with the code base. We hope to improve these with time to make things easier for everyone, but for now this [https://public.etherpad-mozilla.org/p/devtools-intro-pitfalls etherpad] might be a helpful set of notes if you are having trouble. If you find new pitfalls that aren't listed there, feel free to add your own entries, so we know to address them. Also, please come talk to us in #devtools on IRC, as that might be the fastest path to solving the issue.

DevTools/Hacking

2017-04-07T18:46:53Z

Pbrosset: Moved RDP doc to the tree

Want to work on [[DevTools|Firefox Developer Tools]]? You've come to the right place! If you want more information about contributing, check out our guide for [[DevTools/GetInvolved|getting involved]].

= Building, running, updating and rebuilding =

== First Build ==

Follow the instructions on [https://developer.mozilla.org/En/Simple_Firefox_build how to build Firefox]. Roughly:

hg clone http://hg.mozilla.org/mozilla-central
./mach build

For your first build, this should do the trick. If you are going to be building a lot, you may want to set up your [https://developer.mozilla.org/en-US/docs/Configuring_Build_Options .mozconfig file].

== First Run ==

Once you have built Firefox, you can run it with

$ ./mach run

or

$ ./mach run -P development

What is the <code>-P development</code>? It is a flag telling Firefox to use a different [https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data profile], named "development" (this name can be anything you want). If it does not exist the first time you run it, Firefox will open a popup and you can create a new profile with the name you passed in. If you don't specify a profile, <code>mach</code> will create a temporary profile in the path <code><objdir>/tmp/scratch_user</code>.

Once this command runs, you should see a new Firefox window, called "Nightly".

== Incremental Builds ==

Once you've already built Firefox once, if you want to update with the latest changes from the repo, run:

$ hg pull -u

To build with the latest changes or with your own DevTools changes, you can run:

$ ./mach build faster

which is much faster than your first build or clobber builds and should only take a few seconds. You can run your build the same way you did before:

$ ./mach run -P development

If you happen to change any C++ files (which is pretty rare when working on DevTools), you may need a different command for incremental builds:

$ ./mach build binaries

A full <code>./mach build</code> will work for any type of change, it just takes longer to run than the incremental options above.

Note that whenever you pull the latest changes from <tt>fx-team</tt> into your local repository, you may need to "clobber". A "clobber" is similar to a "<code>make clean</code>". You'll know you need to clobber when you get a big error message telling you to do a clobber build after you tried to do an incremental build. To do a clobber build, enter these commands:

$ ./mach clobber
$ ./mach build

== Artifact builds (or: building faster!) ==

If you are '''not''' going to modify any C/C++ code, you could use artifact builds. This method downloads prebuilt components, and then the build process becomes faster.

Essentially, add the following lines to your .mozconfig file:

# Automatically download and use compiled C++ components:
ac_add_options --enable-artifact-builds

# Write build artifacts to:
mk_add_options MOZ_OBJDIR=./objdir-frontend

And then you can follow the normal build process.

On OSX you might want to use <tt>MOZ_OBJDIR=./objdir-frontend.noindex</tt> instead. Using the .noindex file extension prevents spotlight from indexing your objdir, which is slow.

For more information on aspects such as technical limitations, read the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds Artifact Builds] page.

= Configuring your dev profile =

You will want to make a couple of quick changes to the profile you use when running your version of Firefox.

== Enable remote debugging and the Browser Toolbox ==

Open DevTools, and click the "Toolbox Options" gear icon in the top right (the image underneath is outdated). Make sure the following two options are checked:

* '''Enable browser chrome and add-on debugging toolboxes'''
* '''Enable remote debugging'''

These settings allow you to use the [https://developer.mozilla.org/docs/Tools/Browser_Toolbox browser toolbox] to set breakpoints inside of the DevTools code, inspect the DevTools themselves, and let you run the [https://developer.mozilla.org/en-US/docs/Tools/Scratchpad Scratchpad] in the ''Browser'' environment.

[[Image:DevToolsDeveloperSettings.png|center|600px|Settings for developer tools - "Enable Chrome Debugging" and "Enable Remote Debugging"]]

You might also want to change the following preference in '''<tt>about:config</tt>''' to <code>false</code>:

* '''devtools.debugger.prompt-connection'''

This will get rid of the prompt displayed every time you open the browser toolbox.

== Enabling DevTools Logging ==

Depending on what you are working on, you may want to make some changes to your profile to enable more logging. If you type '''<tt>about:config</tt>''' in the URL bar, click through the warning page, and search for '''<tt>devtools</tt>''' you can see some of them.

Add the global "dump" function to all windows which logs strings to stdout.

'''browser.dom.window.dump.enabled''' = true

Dumps all packets sent over the remote debugging protocol to stdout (requires browser.dom.window.dump.enabled):

'''devtools.debugger.log''' = true

Log every event notification from the EventEmitter class (devtools/shared/event-emitter.js) (requires browser.dom.window.dump.enabled)

'''devtools.dump.emit''' = true

Restart the browser to apply configuration changes.

You may also be interested in the remote protocol inspector add-on: https://github.com/firebug/rdp-inspector/wiki

== Enabling DevTools Assertions ==

Highly recommended for DevTools hackers!

Add this to your '''<tt>.mozconfig</tt>''':

ac_add_options --enable-debug-js-modules

Assert your own invariants like this:

const { assert } = require("devtools/shared/DevToolsUtils");
// ...
assert(1 + 1 === 2, "I really hope this is true...");

When assertions are enabled, assertion failures are fatal, log console warnings, and throw errors.

When assertions are not enabled, the <tt>assert</tt> function is a no-op.

It also enables the "debug" builds of certain third party libraries, such as React.

= Developer Tools Directories Overview =

* '''<tt>devtools/shared</tt>''': Code shared by both the DevTools client (front-end UI) and server. If we are using any third party libraries, or importing external repositories into our tree, those libraries generally live here (eg, <tt>devtools/shared/acorn</tt>), assuming they are used by both client and server.
** '''<tt>devtools/shared/client</tt>''': Code for the DevTools [Remote Debugging Protocol http://searchfox.org/mozilla-central/source/devtools/docs/backend/protocol.md] client. (You may wonder why this is not in <tt>devtools/client</tt> below: it's mainly because tests in server also need access to the RDP client.)
** '''<tt>devtools/shared/locales</tt>''': Strings used in either the DevTools server only, or shared with both the client and server
* '''<tt>devtools/server</tt>''': Code for the DevTools [[Remote Debugging Protocol]] server and transport layer.
** '''<tt>devtools/server/actors</tt>''': [[Remote_Debugging_Protocol#Actors RDP Actors]]. Note that if you're modifying the RDP, you may need to worry about [[DevTools/Backwards_Compatibility|backwards compatibilty with older protocol implementations]].
* '''<tt>devtools/client</tt>''': Front end user interfaces for our tools. Should be pretty obvious what is what based on the directory names and each panel we have in our toolbox. This directory is only shipped with desktop Firefox, as opposed to other directories above, which are shipped with all Gecko products (Firefox OS, Firefox for Android, etc.)
** '''<tt>devtools/client/locales</tt>''': Strings used in the DevTools client (front-end UI)
** '''<tt>devtools/client/themes</tt>''': CSS and images used in the DevTools client (front-end UI)

= DevTools Automated Tests =

We use three suites of tests:

* '''xpcshell''': Unit-test style of tests. No browser window, just a JavaScript shell. Mostly testing APIs directly.
* '''mochitest-chrome''': Unit-test style of tests, but with a browser window. Mostly testing APIs that interact with the DOM directly.
* '''mochitest-devtools''': Integration style of tests. Fires up a whole browser window with every test and you can test clicking on buttons, etc.

More information about the different types of tests can be found on the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing MDN automated testing page]

== Running DevTools Tests ==

To run all DevTools tests, regardless of suite type:

$ ./mach test devtools/*

The following sections show more specific commands for running only a single suite or single test in a suite.

=== xpcshell Tests ===

To run all of the xpcshell tests:

$ ./mach xpcshell-test --tag devtools

To run a specific xpcshell test:

$ ./mach xpcshell-test devtools/path/to/the/test_you_want_to_run.js

=== Chrome Mochitests ===

To run the whole suite of chrome mochitests for DevTools:

$ ./mach mochitest -f chrome --tag devtools

To run a specific chrome mochitest:

$ ./mach mochitest devtools/path/to/the/test_you_want_to_run.html

=== DevTools Mochitests ===

To run the whole suite of browser mochitests for DevTools (sit back and relax):

$ ./mach mochitest --subsuite devtools --tag devtools

To run a specific tool's suite of browser mochitests:

$ ./mach mochitest devtools/client/<tool>

For example, run all of the debugger browser mochitests:

$ ./mach mochitest devtools/client/debugger

To run a specific DevTools mochitest:

$ ./mach mochitest devtools/client/path/to/the/test_you_want_to_run.js

Note that the mochitests '''must''' have focus while running.

== Writing Tests ==

When working on a patch for DevTools, there's almost never a reason not to add a new test. If you are fixing a bug, you probably should write a new test to prevent this bug from occurring again. If you're implementing a new feature, you probably should write many new tests to cover the various aspects of this new feature.

You should ask yourself:
* Are there enough tests for my patch?
* Are they the right types of tests?

To help with writing nice, maintainable and consistent DevTools mochitests, please follow our [https://wiki.mozilla.org/DevTools/mochitests_coding_standards DevTools mochitests coding guide].

== Debugging Intermittent Test Failures ==

When a test fails sometimes, but not always, it is called an "intermittent". Handling these is complicated enough that we have a [[DevTools/Intermittents|separate page]] with tips on debugging.

= Finding documentation =

If you read through the source code about something you do not know about, you may find documentation here:

* [http://developer.mozilla.org/ Mozilla Developer Network] has a ton of info about XUL elements, HTML, JS, DOM, Web APIs, Gecko-specific APIs, and more.
* [http://dxr.mozilla.org/mozilla-central/source/ DXR] is a source code search engine - search for symbols you want to learn about, eg. nsIDocument.
* There's some technical [https://dxr.mozilla.org/mozilla-central/source/devtools/docs DevTools documentation in the repository] that you should check.
* And other technical documents on [[DevTools#Internal_Technical_Documentation|on this wiki]]

We recommend [https://support.mozilla.org/en-US/kb/how-search-from-address-bar adding a smart keyword search] for DXR and MDN.
If you still have questions, [[DevTools/GetInvolved#Communication|ask us on IRC]] or leave a comment on the Bugzilla ticket.

= Making and Submitting a Patch =

Before you make any changes, read [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html the documentation on how to use Mozilla's version control].

Before you submit a patch, you should read our [[DevTools/CodingStandards|Coding Standards]] and run [https://wiki.mozilla.org/DevTools/CodingStandards#JS_linting_with_ESLint ESLint] to validate your code changes (to avoid loosing time during code reviews with formatting details for instance). In general, try to be File Consistent. For new files, follow the standards.

Once you have a patch file, add it as an attachment to the Bugzilla ticket you are working on and add the '''feedback?''' or '''review?''' flag depending on if you just want feedback and confirmation you're doing the right thing or if you think the patch is ready to land respectively. Read more about [https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch how to submit a patch and the Bugzilla review cycle here].

You can also take a look at the [[DevTools/Code Review Checklist]] as it contains a list of checks that your reviewer is likely to go over when reviewing your code.

= Coding Standards =

DevTools has some coding standards that your changes should follow:

* [[DevTools/CodingStandards|JavaScript coding standards]]
* [[DevTools/CSSTips|CSS tips]]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/SVG_Guidelines SVG Best practices] and [https://dxr.mozilla.org/mozilla-central/source/devtools/docs/svgs.md guidelines for creating new DevTools SVGs]

= Potential Pitfalls =

Today there are a few techniques and conventions we use that can be confusing, especially when you first start working with the code base. We hope to improve these with time to make things easier for everyone, but for now this [https://public.etherpad-mozilla.org/p/devtools-intro-pitfalls etherpad] might be a helpful set of notes if you are having trouble. If you find new pitfalls that aren't listed there, feel free to add your own entries, so we know to address them. Also, please come talk to us in #devtools on IRC, as that might be the fastest path to solving the issue.

DevTools

2017-04-07T18:45:45Z

Pbrosset: Moved RDP doc to the tree

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

Read [https://devtools-html.github.io/#getting-in-touch this page] for more information about talking with the team, filing bugs, or even fixing a bug yourself!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

DevTools technical docs are available in the DevTools source code under the <code>/devtools/docs</code> directory.
You can read them online here: http://searchfox.org/mozilla-central/source/devtools/docs/SUMMARY.md

Some technical docs are still in the process of being moved to this location, but are available here on the wiki in the meantime:

* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

DevTools

2017-04-07T18:45:09Z

Pbrosset: Moved stream transport to the tree

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

Read [https://devtools-html.github.io/#getting-in-touch this page] for more information about talking with the team, filing bugs, or even fixing a bug yourself!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

DevTools technical docs are available in the DevTools source code under the <code>/devtools/docs</code> directory.
You can read them online here: http://searchfox.org/mozilla-central/source/devtools/docs/SUMMARY.md

Some technical docs are still in the process of being moved to this location, but are available here on the wiki in the meantime:

* [[Remote Debugging Protocol]]
* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

Remote Debugging Protocol Stream Transport

2017-04-07T18:44:20Z

Pbrosset: Moved to the tree

This page moved to the mozilla-central repository with bug 1354587. Find it here: http://searchfox.org/mozilla-central/source/devtools/docs/backend/protocol.md

Remote Debugging Protocol

2017-04-07T18:43:57Z

Pbrosset: Moved to the tree

This page moved to the mozilla-central repository with bug 1354587. Find it here: http://searchfox.org/mozilla-central/source/devtools/docs/backend/protocol.md

DevTools

2017-03-23T13:19:50Z

Pbrosset: Removed best practices since the article moved to devtools/docs/

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

View the [[DevTools/GetInvolved|Getting Involved]] page for more information about talking with the team, filing bugs, or even working on your own [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|first DevTools bug]]!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

DevTools technical docs are available in the DevTools source code under the <code>/devtools/docs</code> directory.
You can read them online here: http://searchfox.org/mozilla-central/source/devtools/docs/SUMMARY.md

Some technical docs are still in the process of being moved to this location, but are available here on the wiki in the meantime:

* [[Remote Debugging Protocol]]
* [[Remote Debugging Protocol Stream Transport]]
* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

DevTools/Actor Best Practices

2017-03-23T13:19:15Z

Pbrosset: Moved to devtools/docs/

Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/backend/actor-best-practices.md

DevTools/Hacking

2017-03-23T13:17:50Z

Pbrosset: Removed this section since it's now in the /devtools/docs/ folder

Want to work on [[DevTools|Firefox Developer Tools]]? You've come to the right place! If you want more information about contributing, check out our guide for [[DevTools/GetInvolved|getting involved]].

= Building, running, updating and rebuilding =

== First Build ==

Follow the instructions on [https://developer.mozilla.org/En/Simple_Firefox_build how to build Firefox]. Roughly:

hg clone http://hg.mozilla.org/mozilla-central
./mach build

For your first build, this should do the trick. If you are going to be building a lot, you may want to set up your [https://developer.mozilla.org/en-US/docs/Configuring_Build_Options .mozconfig file].

== First Run ==

Once you have built Firefox, you can run it with

$ ./mach run

or

$ ./mach run -P development

What is the <code>-P development</code>? It is a flag telling Firefox to use a different [https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data profile], named "development" (this name can be anything you want). If it does not exist the first time you run it, Firefox will open a popup and you can create a new profile with the name you passed in. If you don't specify a profile, <code>mach</code> will create a temporary profile in the path <code><objdir>/tmp/scratch_user</code>.

Once this command runs, you should see a new Firefox window, called "Nightly".

== Incremental Builds ==

Once you've already built Firefox once, if you want to update with the latest changes from the repo, run:

$ hg pull -u

To build with the latest changes or with your own DevTools changes, you can run:

$ ./mach build faster

which is much faster than your first build or clobber builds and should only take a few seconds. You can run your build the same way you did before:

$ ./mach run -P development

If you happen to change any C++ files (which is pretty rare when working on DevTools), you may need a different command for incremental builds:

$ ./mach build binaries

A full <code>./mach build</code> will work for any type of change, it just takes longer to run than the incremental options above.

Note that whenever you pull the latest changes from <tt>fx-team</tt> into your local repository, you may need to "clobber". A "clobber" is similar to a "<code>make clean</code>". You'll know you need to clobber when you get a big error message telling you to do a clobber build after you tried to do an incremental build. To do a clobber build, enter these commands:

$ ./mach clobber
$ ./mach build

== Artifact builds (or: building faster!) ==

If you are '''not''' going to modify any C/C++ code, you could use artifact builds. This method downloads prebuilt components, and then the build process becomes faster.

Essentially, add the following lines to your .mozconfig file:

# Automatically download and use compiled C++ components:
ac_add_options --enable-artifact-builds

# Write build artifacts to:
mk_add_options MOZ_OBJDIR=./objdir-frontend

And then you can follow the normal build process.

On OSX you might want to use <tt>MOZ_OBJDIR=./objdir-frontend.noindex</tt> instead. Using the .noindex file extension prevents spotlight from indexing your objdir, which is slow.

For more information on aspects such as technical limitations, read the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds Artifact Builds] page.

= Configuring your dev profile =

You will want to make a couple of quick changes to the profile you use when running your version of Firefox.

== Enable remote debugging and the Browser Toolbox ==

Open DevTools, and click the "Toolbox Options" gear icon in the top right (the image underneath is outdated). Make sure the following two options are checked:

* '''Enable browser chrome and add-on debugging toolboxes'''
* '''Enable remote debugging'''

These settings allow you to use the [https://developer.mozilla.org/docs/Tools/Browser_Toolbox browser toolbox] to set breakpoints inside of the DevTools code, inspect the DevTools themselves, and let you run the [https://developer.mozilla.org/en-US/docs/Tools/Scratchpad Scratchpad] in the ''Browser'' environment.

[[Image:DevToolsDeveloperSettings.png|center|600px|Settings for developer tools - "Enable Chrome Debugging" and "Enable Remote Debugging"]]

You might also want to change the following preference in '''<tt>about:config</tt>''' to <code>false</code>:

* '''devtools.debugger.prompt-connection'''

This will get rid of the prompt displayed every time you open the browser toolbox.

== Enabling DevTools Logging ==

Depending on what you are working on, you may want to make some changes to your profile to enable more logging. If you type '''<tt>about:config</tt>''' in the URL bar, click through the warning page, and search for '''<tt>devtools</tt>''' you can see some of them.

Add the global "dump" function to all windows which logs strings to stdout.

'''browser.dom.window.dump.enabled''' = true

Dumps all packets sent over the remote debugging protocol to stdout (requires browser.dom.window.dump.enabled):

'''devtools.debugger.log''' = true

Log every event notification from the EventEmitter class (devtools/shared/event-emitter.js) (requires browser.dom.window.dump.enabled)

'''devtools.dump.emit''' = true

Restart the browser to apply configuration changes.

You may also be interested in the remote protocol inspector add-on: https://github.com/firebug/rdp-inspector/wiki

== Enabling DevTools Assertions ==

Highly recommended for DevTools hackers!

Add this to your '''<tt>.mozconfig</tt>''':

ac_add_options --enable-debug-js-modules

Assert your own invariants like this:

const { assert } = require("devtools/shared/DevToolsUtils");
// ...
assert(1 + 1 === 2, "I really hope this is true...");

When assertions are enabled, assertion failures are fatal, log console warnings, and throw errors.

When assertions are not enabled, the <tt>assert</tt> function is a no-op.

It also enables the "debug" builds of certain third party libraries, such as React.

= Developer Tools Directories Overview =

* '''<tt>devtools/shared</tt>''': Code shared by both the DevTools client (front-end UI) and server. If we are using any third party libraries, or importing external repositories into our tree, those libraries generally live here (eg, <tt>devtools/shared/acorn</tt>), assuming they are used by both client and server.
** '''<tt>devtools/shared/client</tt>''': Code for the DevTools [[Remote Debugging Protocol]] client. (You may wonder why this is not in <tt>devtools/client</tt> below: it's mainly because tests in server also need access to the RDP client.)
** '''<tt>devtools/shared/locales</tt>''': Strings used in either the DevTools server only, or shared with both the client and server
* '''<tt>devtools/server</tt>''': Code for the DevTools [[Remote Debugging Protocol]] server and transport layer.
** '''<tt>devtools/server/actors</tt>''': [[Remote_Debugging_Protocol#Actors RDP Actors]]. Note that if you're modifying the RDP, you may need to worry about [[DevTools/Backwards_Compatibility|backwards compatibilty with older protocol implementations]].
* '''<tt>devtools/client</tt>''': Front end user interfaces for our tools. Should be pretty obvious what is what based on the directory names and each panel we have in our toolbox. This directory is only shipped with desktop Firefox, as opposed to other directories above, which are shipped with all Gecko products (Firefox OS, Firefox for Android, etc.)
** '''<tt>devtools/client/locales</tt>''': Strings used in the DevTools client (front-end UI)
** '''<tt>devtools/client/themes</tt>''': CSS and images used in the DevTools client (front-end UI)

= DevTools Automated Tests =

We use three suites of tests:

* '''xpcshell''': Unit-test style of tests. No browser window, just a JavaScript shell. Mostly testing APIs directly.
* '''mochitest-chrome''': Unit-test style of tests, but with a browser window. Mostly testing APIs that interact with the DOM directly.
* '''mochitest-devtools''': Integration style of tests. Fires up a whole browser window with every test and you can test clicking on buttons, etc.

More information about the different types of tests can be found on the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing MDN automated testing page]

== Running DevTools Tests ==

To run all DevTools tests, regardless of suite type:

$ ./mach test devtools/*

The following sections show more specific commands for running only a single suite or single test in a suite.

=== xpcshell Tests ===

To run all of the xpcshell tests:

$ ./mach xpcshell-test --tag devtools

To run a specific xpcshell test:

$ ./mach xpcshell-test devtools/path/to/the/test_you_want_to_run.js

=== Chrome Mochitests ===

To run the whole suite of chrome mochitests for DevTools:

$ ./mach mochitest -f chrome --tag devtools

To run a specific chrome mochitest:

$ ./mach mochitest devtools/path/to/the/test_you_want_to_run.html

=== DevTools Mochitests ===

To run the whole suite of browser mochitests for DevTools (sit back and relax):

$ ./mach mochitest --subsuite devtools --tag devtools

To run a specific tool's suite of browser mochitests:

$ ./mach mochitest devtools/client/<tool>

For example, run all of the debugger browser mochitests:

$ ./mach mochitest devtools/client/debugger

To run a specific DevTools mochitest:

$ ./mach mochitest devtools/client/path/to/the/test_you_want_to_run.js

Note that the mochitests '''must''' have focus while running.

== Writing Tests ==

When working on a patch for DevTools, there's almost never a reason not to add a new test. If you are fixing a bug, you probably should write a new test to prevent this bug from occurring again. If you're implementing a new feature, you probably should write many new tests to cover the various aspects of this new feature.

You should ask yourself:
* Are there enough tests for my patch?
* Are they the right types of tests?

To help with writing nice, maintainable and consistent DevTools mochitests, please follow our [https://wiki.mozilla.org/DevTools/mochitests_coding_standards DevTools mochitests coding guide].

== Debugging Intermittent Test Failures ==

When a test fails sometimes, but not always, it is called an "intermittent". Handling these is complicated enough that we have a [[DevTools/Intermittents|separate page]] with tips on debugging.

= Finding documentation =

If you read through the source code about something you do not know about, you may find documentation here:

* [http://developer.mozilla.org/ Mozilla Developer Network] has a ton of info about XUL elements, HTML, JS, DOM, Web APIs, Gecko-specific APIs, and more.
* [http://dxr.mozilla.org/mozilla-central/source/ DXR] is a source code search engine - search for symbols you want to learn about, eg. nsIDocument.
* There's some technical [https://dxr.mozilla.org/mozilla-central/source/devtools/docs DevTools documentation in the repository] that you should check.
* And other technical documents on [[DevTools#Internal_Technical_Documentation|on this wiki]]

We recommend [https://support.mozilla.org/en-US/kb/how-search-from-address-bar adding a smart keyword search] for DXR and MDN.
If you still have questions, [[DevTools/GetInvolved#Communication|ask us on IRC]] or leave a comment on the Bugzilla ticket.

= Making and Submitting a Patch =

Before you make any changes, read [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html the documentation on how to use Mozilla's version control].

Before you submit a patch, you should read our [[DevTools/CodingStandards|Coding Standards]] and run [https://wiki.mozilla.org/DevTools/CodingStandards#JS_linting_with_ESLint ESLint] to validate your code changes (to avoid loosing time during code reviews with formatting details for instance). In general, try to be File Consistent. For new files, follow the standards.

Once you have a patch file, add it as an attachment to the Bugzilla ticket you are working on and add the '''feedback?''' or '''review?''' flag depending on if you just want feedback and confirmation you're doing the right thing or if you think the patch is ready to land respectively. Read more about [https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch how to submit a patch and the Bugzilla review cycle here].

You can also take a look at the [[DevTools/Code Review Checklist]] as it contains a list of checks that your reviewer is likely to go over when reviewing your code.

= Coding Standards =

DevTools has some coding standards that your changes should follow:

* [[DevTools/CodingStandards|JavaScript coding standards]]
* [[DevTools/CSSTips|CSS tips]]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/SVG_Guidelines SVG Best practices] and [https://dxr.mozilla.org/mozilla-central/source/devtools/docs/svgs.md guidelines for creating new DevTools SVGs]

= Potential Pitfalls =

Today there are a few techniques and conventions we use that can be confusing, especially when you first start working with the code base. We hope to improve these with time to make things easier for everyone, but for now this [https://public.etherpad-mozilla.org/p/devtools-intro-pitfalls etherpad] might be a helpful set of notes if you are having trouble. If you find new pitfalls that aren't listed there, feel free to add your own entries, so we know to address them. Also, please come talk to us in #devtools on IRC, as that might be the fastest path to solving the issue.

DevTools

2017-03-23T08:44:14Z

Pbrosset: Advertising our devtools/docs/ folder instead

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

View the [[DevTools/GetInvolved|Getting Involved]] page for more information about talking with the team, filing bugs, or even working on your own [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|first DevTools bug]]!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

DevTools technical docs are available in the DevTools source code under the <code>/devtools/docs</code> directory.
You can read them online here: http://searchfox.org/mozilla-central/source/devtools/docs/SUMMARY.md

Some technical docs are still in the process of being moved to this location, but are available here on the wiki in the meantime:

* [[Remote Debugging Protocol]]
* [[Remote Debugging Protocol Stream Transport]]
* [[DevTools/Actor Best Practices|Actor Best Practices]]
* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

DevTools

2017-03-23T08:40:53Z

Pbrosset: The highlighter doc now exists in the /devtools/docs folder in the tree. Our wiki page should not link to it. Let's advertise our devtools/docs/ folder instead

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

View the [[DevTools/GetInvolved|Getting Involved]] page for more information about talking with the team, filing bugs, or even working on your own [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|first DevTools bug]]!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

The list below includes technical articles about some of the internals of the DevTools.

== Remote Debugging Protocol ==

* [[Remote Debugging Protocol]]
* [[Remote Debugging Protocol Stream Transport]]
* [https://dxr.mozilla.org/mozilla-central/source/devtools/server/docs/protocol.js.md Protocol.js]
* [[DevTools/Backwards Compatibility|Manage client-server backward compatibility]]
* [[DevTools/Actor Best Practices|Actor Best Practices]]

== Debugger API ==

* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

DevTools

2017-03-23T08:39:43Z

Pbrosset: Removed the links to old projects. These projects are not being worked on now, and we won't resume working on them in this form. So, for the sake of making our DevTools wiki page as simple and easy to move somewhere else as possible, I'm removing these

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

View the [[DevTools/GetInvolved|Getting Involved]] page for more information about talking with the team, filing bugs, or even working on your own [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|first DevTools bug]]!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

The list below includes technical articles about some of the internals of the DevTools.

== Remote Debugging Protocol ==

* [[Remote Debugging Protocol]]
* [[Remote Debugging Protocol Stream Transport]]
* [https://dxr.mozilla.org/mozilla-central/source/devtools/server/docs/protocol.js.md Protocol.js]
* [[DevTools/Backwards Compatibility|Manage client-server backward compatibility]]
* [[DevTools/Actor Best Practices|Actor Best Practices]]

== Debugger API ==

* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Tools ==

* [[DevTools/Highlighter|Inspector Highlighter]]

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

DevTools/Highlighter

2017-03-20T10:04:11Z

Pbrosset: Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/highlighters.md

Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/highlighters.md

Debugger Architecture

2017-03-17T12:55:58Z

Pbrosset: Removed 2 obviously outdated sections. The rest is outdated too, but it makes more sense to keep it and fix it instead.

The Script Debugger in Firefox is composed of a number of separate subsystems that work in concert to provide this user experience. This document will hopefully serve as a guide for everyone who would like to gain a better understanding on how it works, as well as the reasoning behind some of the design decisions.

== Overview ==

There are two main parts to the Script Debugger: the front-end part and the Debugger server that interfaces with the script that is running on the page. These two parts communicate through the [https://wiki.mozilla.org/Remote_Debugging_Protocol#Actors Remote Debugging Protocol] in a traditional client-server architecture, exchanging messages specified as JSON objects. The protocol implementation resides in <tt>toolkit/devtools/debugger</tt>, while the debugger UI can be found in <tt>browser/devtools/debugger</tt>.

== The protocol implementation ==

The debugger server consists of the files in <tt>toolkit/devtools/debugger/server</tt>. The main module is <tt>dbg-server.jsm</tt>. This module creates a sandbox in a separate compartment and loads the <tt>dbg-server.js</tt> code in it. <tt>dbg-server.js</tt> contains the core server logic that handles listening for and responding to connections, handling protocol packets and manipulating actor pools. For more information on actors see the [https://wiki.mozilla.org/Remote_Debugging_Protocol Remote Debugging Protocol]. The other two files in that directory contain definitions for particular families of actors. <tt>dbg-script-actors.js</tt> specifies essential actors for debugging a JavaScript program: thread (or JavaScript context) actors, object actors, (stack) frame actors, environment actors, breakpoint actors, etc. <tt>dbg-browser-actors.js</tt> contains actors pertinent to a web browser, like the root (or browser) actor and tab actors. These modules use the [https://wiki.mozilla.org/Debugger Debugger API] for debugging the script in the page.

Outside of the <tt>server/</tt> directory, we can find 3 separate things. The first is <tt>dbg-client.jsm</tt>, a module for hiding the remote debugging protocol behind an easy to use [https://wiki.mozilla.org/Debugger_Client_API JavaScript API]. The second is <tt>dbg-transport.js</tt>, which contains the low-level code that handles the [https://wiki.mozilla.org/Remote_Debugging_Protocol_Stream_Transport protocol connection] for both client and server. And the last thing is <tt>nsIJSInspector</tt>, a native helper component for entering and exiting nested event loops.

DevTools/Backwards Compatibility

2017-03-17T08:42:12Z

Pbrosset: Deleted the page content since it moved to the tree in bug 1347977

Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/backward-compatibility.md

DevTools

2017-03-16T12:10:26Z

Pbrosset: Moved some old stuff to a new category

= Using Firefox Developer Tools =

Have a question about how to use the features in Developer Tools, or looking for more details about one of the specific tools? See the [https://developer.mozilla.org/en-US/docs/Tools Official Developer Tools Documentation]. If this still doesn't answer your question, [[DevTools/GetInvolved#Communication|let us know]]. We have more information on our Getting Involved page if you need to [[DevTools/GetInvolved#Reporting_Bugs_and_Requesting_Features|report a bug or request a feature]].

= Follow Our Development =

What is the best way to follow along with Firefox Developer Tools? Updates are posted by [https://twitter.com/firefoxdevtools @FirefoxDevTools], we have blog posts on the [https://hacks.mozilla.org/category/developer-tools/ Developer Tools Category on Mozilla Hacks], and you can check out our weekly meetings if you want more information.

= Getting Involved =

View the [[DevTools/GetInvolved|Getting Involved]] page for more information about talking with the team, filing bugs, or even working on your own [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|first DevTools bug]]!

= Weekly Meetings =

We have a weekly meeting to discuss progress on our tools and other topics related to web tooling. View the [https://docs.google.com/document/d/1jWR13lrlKxLKCxYmtH5uS38IPAHFruWN75VVASVt87E Weekly Meeting Google Doc]. Scroll down to see past notes.

Time and phone numbers:
* Tuesdays - 9:00am Pacific, 12:00pm Eastern, 5:00pm UTC
* 650-903-0800 or 650-215-1282 x92 Conf# 99459
* 1-800-707-2533 (pin 369) Conf# 99459 (US)

= New Contributor Documentation =

The list below highlights useful articles for new contributors.

* [[DevTools/GetInvolved|Getting Involved]]
* [[DevTools/GetInvolved#Mentored_and_Good_First_Bugs|Mentored and Good First Bugs]]
* [[DevTools/Hacking|Hacking]]
* [[DevTools/Bug Fixes|Bug Fixes]]

= Internal Technical Documentation =

The list below includes technical articles about some of the internals of the DevTools.

== Remote Debugging Protocol ==

* [[Remote Debugging Protocol]]
* [[Remote Debugging Protocol Stream Transport]]
* [https://dxr.mozilla.org/mozilla-central/source/devtools/server/docs/protocol.js.md Protocol.js]
* [[DevTools/Backwards Compatibility|Manage client-server backward compatibility]]
* [[DevTools/Actor Best Practices|Actor Best Practices]]

== Debugger API ==

* [[Debugger Architecture]]
* [[Debugger Client API]]
* [https://developer.mozilla.org/en-US/docs/Tools/Debugger-API Debugger API] (used in DevTools server)

== Tools ==

* [[DevTools/Highlighter|Inspector Highlighter]]

== Process ==

* [[DevTools/Creating_Good_First_Bugs|Creating Good First Bugs]]
* [[Buildbot/Talos/Tests#DAMP|DevTools Talos Tests (DAMP)]]
* [[DevTools/OperationInstrument|Operation Instrument: Platform Tracing]]

== Some past projects ==

* [[DevTools/WebAudio|Web Audio Editor]]
* [[DevTools/Memory|Memory Tools]]
* [[DevTools/Performance|Performance Tools]]
* [[DevTools/Gaming|Gaming Tools, enhancements for game developers across all tools]]

DevTools/GetInvolved

2017-03-16T11:12:06Z

Pbrosset: Removed the list of resources. This was just a random list of links (some of them to blog posts) that I think was just plain confusing, surely not helping.

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

* '''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

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

Please be aware that we have a [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette].

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] or discuss on the [https://discourse.mozilla-community.org/c/devtools DevTools Discourse category]

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

DevTools/GetInvolved

2017-03-08T08:18:41Z

Pbrosset: Added shader editor as unmaintained, removed Bryan from Debugger, added Fred and Ricky to netmonitor

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

* '''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''': bgrins, jryans, honza, ochameau
* '''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

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/GetInvolved

2017-03-02T14:23:57Z

Pbrosset: added ochameau to about:debugging and rephrased framework

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

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

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/GetInvolved

2017-03-02T09:26:28Z

Pbrosset: added Matteo to RDM

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

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

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/GetInvolved

2017-03-02T08:39:51Z

Pbrosset: Updated the list of people to ping. Removed people not here anymore. Added modules.

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

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

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/GetInvolved

2017-03-01T17:14:11Z

Pbrosset: Updated the list of people to ping

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

* '''about:debugging''': jdescottes
* '''Animation Inspector''': gl, pbro, daisuke
* '''Canvas Debugger''': vporof
* '''Console''': bgrins, nchevobbe
* '''Debugger''': jlast, clarkbw
* '''Developer Toolbar''': jwalker, mikeratcliffe
* '''DOM''': honza
* '''Framework, toolbox''': bgrins, jryans, honza
* '''Inspector''': gl, pbro, zer0, jdescottes, tromey
* '''JSON Viewer''': honza
* '''Memory''': fitzgen
* '''Network Monitor''': honza
* '''Performance''': gregtatum
* '''Responsive Design''': jryans
* '''Scratchpad''': jdescottes
* '''Style Editor''': gl
* '''Storage Inspector''': mikeratcliffe
* '''Web Audio Editor''': jsantell
* '''WebIDE''': jryans, ochameau

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/GetInvolved

2017-03-01T17:08:45Z

Pbrosset: Updated the list of people to ping

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

* '''about:debugging''': jdescottes
* '''Animation Inspector''': gl, pbro
* '''Canvas Debugger''': vporof
* '''Console''': bgrins, nchevobbe
* '''Debugger''': jlast
* '''Developer Toolbar''': jwalker, mikeratcliffe
* '''DOM''': honza
* '''Framework, toolbox''': bgrins, jryans, honza
* '''Inspector''': gl, pbro, zer0, jdescottes, tromey
* '''JSON Viewer''': honza
* '''Memory''': fitzgen
* '''Network Monitor''': honza
* '''Performance''': gtatum
* '''Responsive Design''': jryans
* '''Scratchpad''': jdescottes
* '''Style Editor''': gl
* '''Storage Inspector''': mikeratcliffe
* '''Web Audio Editor''': jsantell
* '''WebIDE''': jryans, ochameau

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/GetInvolved

2017-02-09T16:36:54Z

Pbrosset: Added GL to animation inspector, and made him first for the inspector

This page is the place to learn how to start contributing to the Firefox Developer Tools.

The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web, add-on and Firefox developers. We hope the information on this page will help you become an active member of our community!

If after reading this wiki page, you still aren't sure what your next steps are, [[#Communication|reach out to us on IRC]].

== Communication ==

* Twitter: [https://twitter.com/FirefoxDevTools @FirefoxDevTools]
* Mailing list: [https://lists.mozilla.org/listinfo/dev-developer-tools dev-developer-tools]
* Blog (shared): [http://hacks.mozilla.org/ Mozilla Hacks]
* [[DevTools|Weekly phone calls]]

On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the [[IRC|guide to getting started with IRC]].

We hang out in the '''#devtools''' channel at irc://irc.mozilla.org/devtools

If you have questions about a specific part of the code, here are some good people to ping:

* '''about:debugging''': jdescottes
* '''Animation Inspector''': gl, pbro
* '''Canvas Debugger''': vporof
* '''Console''': bgrins, linclark
* '''Debugger''': ejpbruel, jlongster
* '''Developer Toolbar''': jwalker, mikeratcliffe
* '''DOM''': honza
* '''Framework, toolbox''': bgrins, jryans, honza, jlong
* '''Inspector''': gl, pbro, zer0, tromey
* '''JSON Viewer''': honza
* '''Memory''': fitzgen
* '''Network Monitor''': honza
* '''Performance''': gtatum
* '''Responsive Design''': jryans, gl
* '''Scratchpad''': jdescottes
* '''Style Editor''': gl
* '''Storage Inspector''': mikeratcliffe
* '''UI/UX''': helenvholmes
* '''Web Audio Editor''': jsantell
* '''WebIDE''': jryans, ochameau, janx

== Reporting Bugs and Requesting Features ==

To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.

If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.

== Mentored and Good First Bugs ==

The [http://firefox-dev.tools/ firefox-dev.tools] site can help you find good first bugs and/or mentored bugs.

If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in [[#Communication|#devtools on irc.mozilla.org, or on the dev-developer-tools mailing list]]!

One more useful link: [https://bugzil.la/comp%3A%22Developer%20Tools%22 all open developer tools bugs] might have other items you'd find interesting to work on.

Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.

[[Category:New Contributor Landing Page]]

== Working on the code ==

If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].

== Resources ==

Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!

* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches]
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search]
* [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

DevTools/Bug Fixes

2016-11-17T17:42:14Z

Pbrosset: Added memory leaks

= Bug Fixing in DevTools =

Every quarter the DevTools team devotes a few people to bug fixing and polish bugs that are beyond the team goals.

The bugs in this effort are meant to be the most important polish/paper cut type bugs in each component. They '''should not''' include new features. The focus here is on improving quality and polish in our existing feature set.

Things to be found in these lists:

* actual issues that prevent using the tool easily
* small broken things that prevent a good UX

This page serves as a dashboard for finding those bugs across various issue trackers like Bugzilla and GitHub.

{| class="wikitable"
|-
! Tool
! Description
! Is Priority?
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=top-inspector-bugs Inspector]
| The top inspector bugs:
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: Inspector",
"blocks": "1264624",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
| Priority
|- style="vertical-align:top"
| [https://github.com/devtools-html/debugger.html/issues?q=is%3Aopen+is%3Aissue+label%3Abug Debugger.html]
| The tool is new but has some bugs that will affect the end-user and should be fixed.
| Priority
|- style="vertical-align:top"
| RDM
| <bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: Responsive Design Mode",
"blocks": "1308297",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
| Priority
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1311034 Developer Tools]
|
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools",
"blocks": "1311034",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/buglist.cgi?o2=substring&v2=1307838&resolution=---&query_format=advanced&f2=blocked&component=Developer%20Tools%3A%20Performance%20Tools%20%28Profiler%2FTimeline%29&product=Firefox&list_id=13249379 Performance]
| Some of these bugs may end up getting fixed with the de-XULing process.
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: Performance Tools (Profiler/Timeline)",
"blocks": "1307838",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1308879 about:debugging]
|
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: about:debugging",
"blocks": "1308879",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1308965 DOM Panel]
|
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: DOM",
"blocks": "1308965",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1314815 Memory/compartment Leaks]
|
<bugzilla>
{
"product": "Firefox",
"blocks": "1314815",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1309242 JSON Viewer]
|
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: JSON Viewer",
"blocks": "1309242",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1312444 Storage Inspector]
|
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: Storage Inspector",
"blocks": "1312444",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>
|
|- style="vertical-align:top"
| [https://bugzilla.mozilla.org/show_bug.cgi?id=1317534 console]
|
<bugzilla>
{
"product": "Firefox",
"component": "Developer Tools: Console",
"blocks": "1317534",
"include_fields": "id, priority, summary, product, assigned_to, status"
}
</bugzilla>

Modules/Other

2016-11-16T17:37:40Z

Pbrosset: Added Nicolas Chevobbe as a DevTools peer

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Add-on SDK
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Myk Melez, Will Bamberg
|forum=http://groups.google.com/group/mozilla-labs-jetpack
|source_dirs=https://github.com/mozilla/addon-sdk
|url=https://wiki.mozilla.org/Jetpack
|components=Add-on SDK
}}

{{Module
|name=Android Background Services
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.
|owner=[mailto:rnewman@mozilla.com Richard Newman]
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox]
|forum=mozilla.dev.platforms.mobile
|source_dirs=https://github.com/mozilla-services/android-sync
|url=https://wiki.mozilla.org/Android/Services
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]
}}

{{Module
|name=BrowserID
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..)
|owner=Ben Adida
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons
|source_dirs=
BrowserID server code: https://github.com/mozilla/browserid,
BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity
|forum=https://lists.mozilla.org/listinfo/dev-identity
}}

{{Module
|name=ChatZilla
|description=IRC client
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]
|group=dev-apps-chatzilla
|source_dirs=extensions/irc/
|url=http://chatzilla.hacksrus.com/
|components=Other Applications::ChatZilla
}}

{{Module
|name=Composer
|description=Editor/Composer
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-tech-editor
|source_dirs=editor/
|url=http://www.mozilla.org/editor
|components=Composer
}}

{{Module
|name=Content Services Infrastructure
|description=A set of data services that allow for content to be served and measured
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]
|peers=[mailto:tspurway@mozilla.com Tim Spurway]
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx
|url=https://wiki.mozilla.org/Tiles
|components=Content Services
}}

{{Module
|name=Devtools
|description=Mozilla Developer Tools
|owner=[mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jwalker@mozilla.com Joe Walker]
|peers=[mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes],[mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:ejpbruel@mozilla.com Eddy Bruel], [mailto:jlongster@mozilla.com James Long], [mailto:jsantell@mozilla.com Jordan Santell], [mailto:ttromey@mozilla.com Tom Tromey], [mailto:jsnajdr@gmail.com Jaroslav Šnajdr], [mailto:lclark@mozilla.com Lin Clark], [mailto:jlaster@mozilla.com Jason Laster], [mailto:odvarko@gmail.com Jan 'Honza' Odvarko], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:mferretti@mozilla.com Matteo Ferretti], [mailto:chevobbe.nicolas@gmail.com Nicolas Chevobbe], [mailto:sfink@mozilla.com Steve Fink] (heapsnapshot code)
|peersemeritus=Mihai Șucan, Rob Campbell, Heather Arthur, Anton Kovalyov, Brandon Benvie
|group=dev-developer-tools
|source_dirs=devtools
|url=https://wiki.mozilla.org/DevTools
|components=Firefox::Developer Tools
}}

{{Module
|name=Directory SDK
|description=Tools and SDKs for accessing LDAP Directories.
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]
|group=dev-tech-ldap
|source_dirs=directory/
|url=http://www.mozilla.org/directory
|components=Directory
}}

{{Module
|name=DOM Inspector
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=
|source_dirs=extensions/inspector/, layout/inspector/
|url=
|components=Other Applications::DOM Inspector
}}

{{Module
|name=Firefox for Android (Fennec)
|description=Mobile Web Browser
|owner=[mailto:mleibovic@mozilla.com Margaret Leibovic]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:nalexander@mozilla.com Nick Alexander], [https://mozillians.org/en-US/u/myk/ Myk Melez], [mailto:mcomella@mozilla.com Michael Comella], [mailto:skaspari@mozilla.com Sebastian Kaspari]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=mobile/
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for Android
}}

{{Module
|name=Firefox for iOS (Fennec)
|description=Mobile Web Browser
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:sleroux@mozilla.com Steph Leroux], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=https://github.com/mozilla/firefox-ios
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for iOS
}}

{{Module
|name=Firefox Accounts
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.
|owner=[mailto:ckarlof@mozilla.com Chris Karlof]
|peers=[mailto:dcoates@mozilla.com Danny Coates], [mailto:zcarter@mozilla.com Zach Carter], [mailto:rfkelly@mozilla.com Ryan Kelly], [mailto:chilts@mozilla.com Andrew Chilton], [mailto:fmarier@mozilla.com Francois Marier], [mailto:smcarthur@mozilla.com Sean McArthur], [mailto:nchapman@mozilla.com Nick Chapman], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:jrgm@mozilla.com John Morrison], [mailto:pdehaan@mozilla.com Peter deHaan]
|group=
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts
}}

{{Module
|name=Firefox for Metro
|description=Touch-screen-friendly browser for Windows
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]
|forum=https://mail.mozilla.org/listinfo/metro
|source_dirs=browser/metro
|url=https://wiki.mozilla.org/Firefox/Metro
|components=Firefox for Metro
}}

{{Module
|name=Loop aka Firefox Hello
|description=Voice and Video Collaboration System
|owner=[mailto:standard8@mozilla.com Mark Banner]
|peers=[mailto:abr@mozilla.com Adam Roach], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client
|url=https://wiki.mozilla.org/Loop
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop
}}

{{Module
|name=Mozilla Location Service (MLS)
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]
|peers=
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/ichnaea
|url=https://location.services.mozilla.com
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues
}}

{{Module
|name=Mozilla Stumbler ("MozStumbler")
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).
|owner=Garvan Keeley
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/MozStumbler
|url=https://location.services.mozilla.com
|components=https://github.com/mozilla/MozStumbler/issues
}}

{{Module
|name=Sync
|description=Firefox Sync client
|owner=[mailto:mconnor@mozilla.com Mike Connor]
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen
|group=
|source_dirs=services/sync/
|url=https://wiki.mozilla.org/Services/Process/Code_Review
|components=Sync
}}

{{Module
|name=Party Tool
|description=PHP-based party tool used for Firefox Party
|owner=[mailto:rflint@ryanflint.com Ryan Flint]
|peers=Mike Morgan, [mailto:reed@reedloden.com Reed Loden]
|group=dev-apps-webtools
|source_dirs=webtools/partytool/
|url=http://wiki.mozilla.org/Webtools:PartyTool
|components=
}}

{{Module
|name=Penelope
|description=Eudora-like functionality and theme added to Thunderbird.
|owner=Jeff Beckley
|peers=
|group=
|source_dirs=penelope/
|url=https://wiki.mozilla.org/Penelope
|components=Penelope
}}

{{Module
|name=Popcorn.js
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/popcorn-js/
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview
}}

{{Module
|name=Popcorn Maker
|description=An SDK for authoring Popcorn projects.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/butter/
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview
}}

{{Module
|name=Rhino
|description=JavaScript interpreter/compiler implemented in Java
|owner=[mailto:greg@apigee.com Greg Brail]
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]
|group=dev-tech-js-engine
|source_dirs=js/rhino/
|url=http://www.mozilla.org/rhino/
|components=Rhino
}}

{{Module
|name=Standalone Composer
|description=Standalone editor/composer based on mozilla/toolkit
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=dev-tech-editor,dev-apps-other
|source_dirs=composer/
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu
|components=
}}

{{Module
|name=URL Classifier
|description=Database and list-based classification of URL resources,
such as Tracking Protection and SafeBrowsing.
|owner=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client), [mailto:rtilder@mozilla.com Ryan Tilder] (server)
|peers=[mailto:francois@mozilla.com François Marier], [mailto:rkelly@mozilla.com Ryan Kelly]
|group=mozilla.dev.platform
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar
|url=
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation
|components=
}}

{{Module
|name=Venkman
|description=JavaScript Debugger frontend
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-apps-js-debugger
|source_dirs=extensions/venkman/
|url=http://www.mozilla.org/projects/venkman
http://www.hacksrus.com/~ginda/venkman/
|components=Other Applications::Venkman JS Debugger
}}

Modules/Other

2016-11-04T14:19:07Z

Pbrosset: Changing the list of owners and peers of the devtools module. This was discussed with Joe Walker who discussed with Dave Camp.

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Add-on SDK
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Myk Melez, Will Bamberg
|forum=http://groups.google.com/group/mozilla-labs-jetpack
|source_dirs=https://github.com/mozilla/addon-sdk
|url=https://wiki.mozilla.org/Jetpack
|components=Add-on SDK
}}

{{Module
|name=Android Background Services
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.
|owner=[mailto:rnewman@mozilla.com Richard Newman]
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox]
|forum=mozilla.dev.platforms.mobile
|source_dirs=https://github.com/mozilla-services/android-sync
|url=https://wiki.mozilla.org/Android/Services
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]
}}

{{Module
|name=BrowserID
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..)
|owner=Ben Adida
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons
|source_dirs=
BrowserID server code: https://github.com/mozilla/browserid,
BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity
|forum=https://lists.mozilla.org/listinfo/dev-identity
}}

{{Module
|name=ChatZilla
|description=IRC client
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]
|group=dev-apps-chatzilla
|source_dirs=extensions/irc/
|url=http://chatzilla.hacksrus.com/
|components=Other Applications::ChatZilla
}}

{{Module
|name=Composer
|description=Editor/Composer
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-tech-editor
|source_dirs=editor/
|url=http://www.mozilla.org/editor
|components=Composer
}}

{{Module
|name=Content Services Infrastructure
|description=A set of data services that allow for content to be served and measured
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]
|peers=[mailto:tspurway@mozilla.com Tim Spurway]
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx
|url=https://wiki.mozilla.org/Tiles
|components=Content Services
}}

{{Module
|name=Devtools
|description=Mozilla Developer Tools
|owner=[mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jwalker@mozilla.com Joe Walker]
|peers=[mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes],[mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:ejpbruel@mozilla.com Eddy Bruel], [mailto:jlongster@mozilla.com James Long], [mailto:jsantell@mozilla.com Jordan Santell], [mailto:ttromey@mozilla.com Tom Tromey], [mailto:jsnajdr@gmail.com Jaroslav Šnajdr], [mailto:lclark@mozilla.com Lin Clark], [mailto:jlaster@mozilla.com Jason Laster], [mailto:odvarko@gmail.com Jan 'Honza' Odvarko], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:mferretti@mozilla.com Matteo Ferretti], [mailto:sfink@mozilla.com Steve Fink] (heapsnapshot code)
|peersemeritus=Mihai Șucan, Rob Campbell, Heather Arthur, Anton Kovalyov, Brandon Benvie
|group=dev-developer-tools
|source_dirs=devtools
|url=https://wiki.mozilla.org/DevTools
|components=Firefox::Developer Tools
}}

{{Module
|name=Directory SDK
|description=Tools and SDKs for accessing LDAP Directories.
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]
|group=dev-tech-ldap
|source_dirs=directory/
|url=http://www.mozilla.org/directory
|components=Directory
}}

{{Module
|name=DOM Inspector
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=
|source_dirs=extensions/inspector/, layout/inspector/
|url=
|components=Other Applications::DOM Inspector
}}

{{Module
|name=Firefox for Android (Fennec)
|description=Mobile Web Browser
|owner=[mailto:mleibovic@mozilla.com Margaret Leibovic]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:nalexander@mozilla.com Nick Alexander], [https://mozillians.org/en-US/u/myk/ Myk Melez], [mailto:mcomella@mozilla.com Michael Comella], [mailto:skaspari@mozilla.com Sebastian Kaspari]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=mobile/
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for Android
}}

{{Module
|name=Firefox for iOS (Fennec)
|description=Mobile Web Browser
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:sleroux@mozilla.com Steph Leroux], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=https://github.com/mozilla/firefox-ios
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for iOS
}}

{{Module
|name=Firefox Accounts
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.
|owner=[mailto:ckarlof@mozilla.com Chris Karlof]
|peers=[mailto:dcoates@mozilla.com Danny Coates], [mailto:zcarter@mozilla.com Zach Carter], [mailto:rfkelly@mozilla.com Ryan Kelly], [mailto:chilts@mozilla.com Andrew Chilton], [mailto:fmarier@mozilla.com Francois Marier], [mailto:smcarthur@mozilla.com Sean McArthur], [mailto:nchapman@mozilla.com Nick Chapman], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:jrgm@mozilla.com John Morrison], [mailto:pdehaan@mozilla.com Peter deHaan]
|group=
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts
}}

{{Module
|name=Firefox for Metro
|description=Touch-screen-friendly browser for Windows
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]
|forum=https://mail.mozilla.org/listinfo/metro
|source_dirs=browser/metro
|url=https://wiki.mozilla.org/Firefox/Metro
|components=Firefox for Metro
}}

{{Module
|name=Loop aka Firefox Hello
|description=Voice and Video Collaboration System
|owner=[mailto:standard8@mozilla.com Mark Banner]
|peers=[mailto:abr@mozilla.com Adam Roach], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client
|url=https://wiki.mozilla.org/Loop
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop
}}

{{Module
|name=Mozilla Location Service (MLS)
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]
|peers=
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/ichnaea
|url=https://location.services.mozilla.com
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues
}}

{{Module
|name=Mozilla Stumbler ("MozStumbler")
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).
|owner=Garvan Keeley
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/MozStumbler
|url=https://location.services.mozilla.com
|components=https://github.com/mozilla/MozStumbler/issues
}}

{{Module
|name=Sync
|description=Firefox Sync client
|owner=[mailto:mconnor@mozilla.com Mike Connor]
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen
|group=
|source_dirs=services/sync/
|url=https://wiki.mozilla.org/Services/Process/Code_Review
|components=Sync
}}

{{Module
|name=Party Tool
|description=PHP-based party tool used for Firefox Party
|owner=[mailto:rflint@ryanflint.com Ryan Flint]
|peers=Mike Morgan, [mailto:reed@reedloden.com Reed Loden]
|group=dev-apps-webtools
|source_dirs=webtools/partytool/
|url=http://wiki.mozilla.org/Webtools:PartyTool
|components=
}}

{{Module
|name=Penelope
|description=Eudora-like functionality and theme added to Thunderbird.
|owner=Jeff Beckley
|peers=
|group=
|source_dirs=penelope/
|url=https://wiki.mozilla.org/Penelope
|components=Penelope
}}

{{Module
|name=Popcorn.js
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/popcorn-js/
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview
}}

{{Module
|name=Popcorn Maker
|description=An SDK for authoring Popcorn projects.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/butter/
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview
}}

{{Module
|name=Rhino
|description=JavaScript interpreter/compiler implemented in Java
|owner=[mailto:greg@apigee.com Greg Brail]
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]
|group=dev-tech-js-engine
|source_dirs=js/rhino/
|url=http://www.mozilla.org/rhino/
|components=Rhino
}}

{{Module
|name=Standalone Composer
|description=Standalone editor/composer based on mozilla/toolkit
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=dev-tech-editor,dev-apps-other
|source_dirs=composer/
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu
|components=
}}

{{Module
|name=URL Classifier
|description=Database and list-based classification of URL resources,
such as Tracking Protection and SafeBrowsing.
|owner=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client), [mailto:rtilder@mozilla.com Ryan Tilder] (server)
|peers=[mailto:francois@mozilla.com François Marier], [mailto:rkelly@mozilla.com Ryan Kelly]
|group=mozilla.dev.platform
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar
|url=
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation
|components=
}}

{{Module
|name=Venkman
|description=JavaScript Debugger frontend
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-apps-js-debugger
|source_dirs=extensions/venkman/
|url=http://www.mozilla.org/projects/venkman
http://www.hacksrus.com/~ginda/venkman/
|components=Other Applications::Venkman JS Debugger
}}

Bug Component Triagers

2016-10-03T10:08:56Z

Pbrosset: Updated about:debugging's triager

=Who triages which component=

{{warning|This page is in the middle of a major update. We are editing this inside of a google doc for convenience and will update this page when complete. [[User:Emceeaich|Emceeaich]] ([[User talk:Emceeaich|talk]])}}

==Core==
{| class="wikitable sortable"
|-
! Component !! Responsible triager !! Notes
|-
| Audio/Video || Maire and Anthony || https://wiki.mozilla.org/Media/Bugs#Core::Audio.2FVideo_.28Main_Component.29_Queries NOTE: This component is meant as a temporary place for Media bugs. Folks put media bugs here when they aren't sure which A/V component they really belong in.
|-
| Audio/Video: cubeb || Maire || https://wiki.mozilla.org/Media/Bugs#Core::Audio.2FVideo_-_Cubeb_Bugzilla_Queries
|-
| Audio/Video: GMP || Maire || https://wiki.mozilla.org/Media/Bugs#Core::Audio.2FVideo_-_GMP_.28Gecko_Media_Plugin.29_Bugzilla_Queries
|-
| Audio/Video: MediaStreamGraph || Maire || https://wiki.mozilla.org/Media/Bugs#Core::Audio.2FVideo_-_MediaStreamGraph_Bugzilla_Queries
|-
| Audio/Video: Playback || Anthony ||
|-
| Audio/Video: Recording || Maire || https://wiki.mozilla.org/Media/Bugs#Core::Audio.2FVideo_-_Recording_Bugzilla_Queries
|-
| AutoConfig (Mission Control Desktop) || ||
|-
| Build Config || ||
|-
| Canvas: 2D || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Canvas: WebGL || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| CSS Parsing and Computation || ||
|-
| Disability Access APIs || DBolter ||
|-
| DMD || ||
|-
| Document Navigation || Overholt ||
|-
| DOM || Overholt ||
|-
| DOM: Animation || ||
|-
| DOM: Apps || || Myk? Archive?
|-
| DOM: Contacts || || Gregor? B2G-specific
|-
| DOM: Content Processes || Overholt||
|-
| DOM: Core & HTML || Overholt ||
|-
| DOM: CSS Object Model || ||
|-
| DOM: Device Interfaces || Overholt ||
|-
| DOM: Events || Overholt ||
|-
| DOM: IndexedDB || Overholt ||
|-
| DOM: Push Notifications || Overholt ||
|-
| DOM: Security || ckerschb ||
|-
| DOM: Service Workers || Overholt ||
|-
| DOM: Workers || Overholt ||
|-
| Drag and Drop || ||
|-
| Editor || ||
|-
| Embedding: APIs || ||
|-
| Embedding: GRE Core || ||
|-
| Embedding: Mac || ||
|-
| Embedding: MFC Embed || ||
|-
| Embedding: Packaging || ||
|-
| Event Handling || Overholt ||
|-
| File Handling || ||
|-
| Find Backend || ||
|-
| FxAccounts || ||
|-
| Gecko Profiler || ||
|-
| General || ||
|-
| Geolocation || ||
|-
| GFX: Color Management || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Graphics || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Graphics: Layers || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Graphics: Text || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Hardware Abstraction Layer (HAL) || ||
|-
| History: Global || ||
|-
| HTML: Form Submission || ||
|-
| HTML: Parser || Overholt ||
|-
| Identity || ||
|-
| Image Blocking || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| ImageLib || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Internationalization || ||
|-
| IPC || Overholt ||
|-
| JavaScript Engine || ||
|-
| JavaScript Engine: JIT || ||
|-
| JavaScript: GC || ||
|-
| JavaScript: Internationalization API || ||
|-
| JavaScript: Standard Library || ||
|-
| js-ctypes || ||
|-
| Keyboard: Navigation || ||
|-
| Layout || ||
|-
| Layout: Block and Inline || ||
|-
| Layout: Floats || ||
|-
| Layout: Form Controls || ||
|-
| Layout: HTML Frames || ||
|-
| Layout: Images || ||
|-
| Layout: Misc Code || ||
|-
| Layout: R & A Pos || ||
|-
| Layout: Tables || ||
|-
| Layout: Text || ||
|-
| Layout: View Rendering || ||
|-
| Localization || ||
|-
| mach || ||
|-
| MathML || ||
|-
| Memory Allocator || ||
|-
| MFBT || ||
|-
| mozglue || ||
|-
| Nanojit || ||
|-
| Networking || ||
|-
| Networking: Cache || ||
|-
| Networking: Cookies || ||
|-
| Networking: DNS || ||
|-
| Networking: Domain Lists || ||
|-
| Networking: File || ||
|-
| Networking: FTP || ||
|-
| Networking: HTTP || ||
|-
| Networking: JAR || ||
|-
| Networking: WebSockets || ||
|-
| Panning and Zooming || Milan || https://wiki.mozilla.org/Platform/GFX/TriageSchedule
|-
| Permission Manager || ||
|-
| Platform Fuzzing Team || ||
|-
| Plug-ins || ||
|-
| Preferences: Backend || ||
|-
| Print Preview || ||
|-
| Printing: Output || ||
|-
| Printing: Setup || ||
|-
| Profile: BackEnd || ||
|-
| Profile: Migration || ||
|-
| Profile: Roaming || ||
|-
| QuickLaunch (AKA turbo mode) || ||
|-
| RDF || ||
|-
| Rewriting and Analysis || ||
|-
| Security || ||
|-
| Security: CAPS || ||
|-
| Security: Process Sandboxing || ||
|-
| Security: PSM || dkeeler ||
|-
| Security: UI || dkeeler ||
|-
| Selection || ||
|-
| Serializers || Overholt ||
|-
| Spelling checker || ||
|-
| SQL || ||
|-
| String || ||
|-
| SVG || ||
|-
| Tracking || ||
|-
| Untriaged || ||
|-
| Web Audio || Maire || https://wiki.mozilla.org/Media/Bugs#Web_Audio_Bugzilla_Queries
|-
| Web Services || ||
|-
| Web Speech || ||
|-
| WebDAV || ||
|-
| WebRTC || Maire || https://wiki.mozilla.org/Media/Bugs#WebRTC_Bugzilla_Queries
|-
| WebRTC: Audio/Video || Maire || https://wiki.mozilla.org/Media/Bugs#WebRTC_Bugzilla_Queries
|-
| WebRTC: Networking || Maire || https://wiki.mozilla.org/Media/Bugs#WebRTC_Bugzilla_Queries
|-
| WebRTC: Signaling || Maire || https://wiki.mozilla.org/Media/Bugs#WebRTC_Bugzilla_Queries
|-
| Widget || ||
|-
| Widget: Android || ||
|-
| Widget: Cocoa || ||
|-
| Widget: Gonk || ||
|-
| Widget: Gtk || ||
|-
| Widget: Qt || ||
|-
| Widget: Win32 || ||
|-
| Widget: WinRT || ||
|-
| X-remote || ||
|-
| XBL || ||
|-
| XForms || ||
|-
| XML || Overholt ||
|-
| XP Toolkit/Widgets: Menus || ||
|-
| XP Toolkit/Widgets: XUL || ||
|-
| XPCOM || ||
|-
| XPConnect || ||
|-
| XSLT || Overholt ||
|-
| XUL || ||
|-
|}

==Firefox==
{| class="wikitable sortable"
|-
! Component !! Responsible triager !! Notes
|-
| Bookmarks & History || ||
|-
| Build Config || ||
|-
| Developer Tools || ||
|-
| Developer Tools: 3D View || vporof ||
|-
| Developer Tools: about:debugging || jdescottes ||
|-
| Developer Tools: Animation Inspector || pbrosset ||
|-
| Developer Tools: Canvas Debugger || gregtatum ||
|-
| Developer Tools: Computed Styles Inspector || pbrosset, tromey ||
|-
| Developer Tools: Console || bgrins ||
|-
| Developer Tools: CSS Rules Inspector || pbrosset, tromey ||
|-
| Developer Tools: Debugger || jlong, ejpbruel ||
|-
| Developer Tools: Font Inspector || pbrosset ||
|-
| Developer Tools: Framework || bgrins, honza, jlong, jryans ||
|-
| Developer Tools: Graphic Commandline and Toolbar || jwalker, mikeratcliffe ||
|-
| Developer Tools: Inspector || pbrosset, zer0 ||
|-
| Developer Tools: JSON Viewer || honza ||
|-
| Developer Tools: Memory || fitzgen ||
|-
| Developer Tools: Netmonitor || honza ||
|-
| Developer Tools: Object Inspector || vporof ||
|-
| Developer Tools: Performance Tools (Profiler/Timeline) || gregtatum ||
|-
| Developer Tools: Responsive Mode || jryans ||
|-
| Developer Tools: Scratchpad || fitzgen ||
|-
| Developer Tools: Source Editor || gl ||
|-
| Developer Tools: Storage Inspector || mratcliffe ||
|-
| Developer Tools: Style Editor || gl ||
|-
| Developer Tools: User Stories || clarkbw ||
|-
| Developer Tools: Web Audio Editor || jsantell ||
|-
| Developer Tools: WebGL Shader Editor || vporof ||
|-
| Developer Tools: WebIDE || jryans, janx, ochameau ||
|-
| Device Permissions || ||
|-
| Disability Access || ||
|-
| Downloads Panel || ||
|-
| Extension Compatibility || ||
|-
| File Handling || ||
|-
| General || ||
|-
| Help Documentation || ||
|-
| Installer || Stephen Pohl, Robert Strong ||
|-
| Keyboard Navigation || ||
|-
| Location Bar || ||
|-
| Menus || ||
|-
| Microsummaries || ||
|-
| Migration || ||
|-
| New Tab Page || ||
|-
| Page Info Window || ||
|-
| Panorama || ||
|-
| PDF Viewer || ||
|-
| Plugin Click-To-Activate Whitelist || ||
|-
| Pocket || ||
|-
| Preferences || ||
|-
| Private Browsing || ||
|-
| Reading List || ||
|-
| RSS Discovery and Preview || ||
|-
| Screen Sharing Whitelist || ||
|-
| Search || ||
|-
| Security || ||
|-
| Session Restore || ||
|-
| Shell Integration || ||
|-
| Shumway || ||
|-
| SocialAPI || ||
|-
| SocialAPI: Providers || ||
|-
| Sync || ||
|-
| Tabbed Browser || ||
|-
| Theme || ||
|-
| Toolbars and Customization || ||
|-
| Tours || ||
|-
| Translation || ||
|-
| Untriaged || ||
|-
| Web Apps || ||
|-
| Webapp Runtime || ||
|-
| WinQual Reports || ||
|}

==Toolkit==
{| class="wikitable sortable"
|-
! Component !! Responsible triager !! Notes
|- || ||
| about:memory || ||
|- || ||
| Add-ons Manager || ||
|- || ||
| Application Update || Stephen Pohl, Robert Strong ||
|- || ||
| Async Tooling || ||
|- || ||
| Autocomplete || ||
|- || ||
| Breakpad Integration || ||
|- || ||
| Build Config || ||
|- || ||
| Download Manager || ||
|- || ||
| Error Console || ||
|- || ||
| Find Toolbar || ||
|- || ||
| Forget About Site || ||
|- || ||
| Form Manager || ||
|- || ||
| General || ||
|- || ||
| Help Viewer || ||
|- || ||
| Microformats || ||
|- || ||
| Notifications and Alerts || ||
|- || ||
| NSIS Installer || Stephen Pohl, Robert Strong ||
|- || ||
| OS.File || ||
|- || ||
| Password Manager || ||
|- || ||
| Performance Monitoring || ||
|- || ||
| Places || ||
|- || ||
| Preferences || ||
|- || ||
| Printing || ||
|- || ||
| Reader Mode || ||
|- || ||
| Safe Browsing || fmarier/gcp ||
|- || ||
| Security || ||
|- || ||
| Spatial Navigation || ||
|- || ||
| Startup and Profile System || ||
|- || ||
| Storage || ||
|- || ||
| Telemetry || ||
|- || ||
| Themes || ||
|- || ||
| Toolbars and Toolbar Customization || ||
|- || ||
| Video/Audio Controls || ||
|- || ||
| View Source || ||
|- || ||
| WebExtensions || ||
|- || ||
| XUL Widgets || ||
|- || ||
| XULRunner || ||
|}

==Fennec==
{| class="wikitable sortable"
|-
! Component !! Responsible triager !! Notes
|-
| Add-on Manager || Margaret, andym ||
|-
| Audio/Video || snorp ||
|-
| Awesomescreen || ahunt ||
|-
| Build Config & IDE Support || Nick Alexander ||
|-
| Data Providers || Richard Newman ||
|-
| Download Manager || Sebastian ||
|-
| Family Friendly Browsing || Sebastian ||
|-
| Favicon Handling || Margaret ||
|-
| Firefox Accounts || Richard Newman ||
|-
| First Run || Chenxia Liu ||
|-
| GeckoView || snorp ||
|-
| General || Margaret ||
|-
| Graphics, Panning and Zooming || Milan, snorp ||
|-
| JimDB || Jim Chen (obviously) ||
|-
| Keyboards and IME || Jim Chen ||
|-
| Locale switching and selection || rnewman ||
|-
| Logins, Passwords and Form Fill || Margaret ||
|-
| Overlays || mcomella ||
|-
| Plugins || lol ||
|-
| Profile Handling || rnewman ||
|-
| Reader View || Margaret ||
|-
| Reading List || Margaret || We should get rid of this soon.
|-
| Screencasting || mfinkle ||
|-
| Search Activity || Margaret ||
|-
| Settings and Preferences || Margaret ||
|-
| Testing || Kevin Brosnan, Nick Alexander ||
|-
| Text Selection || snorp ||
|-
| Theme and Visual Design || mcomella ||
|-
| Web Apps || Margaret || We should get rid of this soon.
|}