Shared components used by Firefox and other Mozilla software, including handling of Web content; Gecko, HTML, CSS, layout, DOM, scripts, images, networking, etc. Issues with web page layout probably go here, while Firefox user interface issues belong in the Firefox
product. (More info
Select a component to see open bugs in that component:
For problems related to media (video/audio) -- especially when the reporter is not sure which area of the media stack the problem is in. This category will mostly be for untriaged video/audio issues. Bugs in this category will typically be moved to another media category during the triage process.
Any bug in libcubeb. Typically audio output and input bugs would go here
Any bug in the Gecko Media Plugin framework. This is the code that glues the openh264 plugin and EME plugins to the browser.
Any bug related to MediaStreams, MediaStreamTracks, TrackUnions and the MediaStream GraphDriver.
For problems related to the HTML 5 media elements (<video> and <audio>) -- including WebM, MP4, MSE and EME issues. This would also typically include decoding problems in the codecs themselves (e.g. VP8, VP9, H.264, AAC) experienced during playback.
Issues relating to recording/encoding of audio and video using the HTML5 MediaRecorder API.
For bugs using an AutoConfig (mozilla.cfg) file to configure Firefox or other Mozilla applications. NOT for Thunderbird Autoconfiguration.
File bugs here for all issues related to the Gecko/Firefox build config and build system. This is the component for most issues related to Makefile files, moz.build files, configure, packaging, mozboot, mach build, mach bootstrap, mozbuild, and many other related components. If you run into an issue building Firefox, Fennec, or xulrunner, file bugs here.
Bugs with the HTML5 <canvas>
element, its XUL sibling, and related rendering contexts.
Bugs with the WebGL Canvas Context.
Bugs in the handling of CSS stylesheets and the computation of style from CSS stylesheets and HTML attributes.
For bugs in the rendering, see the Layout components.
Description: This component relates to bugs in our support for accessibility APIs on the various platforms. Accessibility APIs allow 3rd party products, such as screen readers used by visually impaired users, to communicate with our content and UI. The APIs we support specifically are MSAA on Windows and
ATK on UNIX/Linux (Apple has not yet published specs for an accessibility API on OS X). This component is not for keyboard, focus or any accessibility bugs other than those relating to the APIs we export.
Issues relating to DMD (dark matter detector), the tool for verifying memory reporters.
Docshell acts as the glue that initiates and monitors document loading and associates documents to their view for rendering. Previously called Webshell.
For bugs in DOM
support which do not fit into any other DOM Component. This is the right component for issues with <base href="">
. (More info
Bugs related to Gecko's navigator.mozApps DOM API
Bugs related to Gecko's Contacts API.
Issues related to implementation of content processes in B2G and Firefox, especially the code in dom/ipc (more info
For bugs in our DOM Style
Examples of appropriate bugs: document.styleSheets doesn't hold missing
file:// stylesheets; crash setting element.style.color to 'red'.
This is not the place for most style bugs unless they involve scripting. See the Style System and Layout components.
This component covers WebAPIs
exposing device interfaces for communication, networking, multimedia, etc.
For bugs in our DOM Events
support. This component deals with event bubbling, event handling, and interfaces such as UIEvent.
Examples of appropriate bugs: cannot cancel 'submit' event; crash when handling a DOMNodeInserted event after inserting a node into anonymous content.
Bugs related to the Flyweb project - implementation, discovery, networking and UX.
This component covers the IndexedDB
implementation in Gecko.
Push Notifications wake up and notify web-apps when a remote server has something of interest for the web-app.
Native content-based security features including: Content Security Policy (CSP), Mixed Content Blocker (MCB), and Safe Browsing.
This component covers the Web Workers
implementation in Gecko.
Description: Problems with drag and drop functionality anywhere in the applications.
For bugs in plaintext or HTML editing support in Gecko. This covers the editing support behind things such as <input type=text>, <textarea>, contenteditable/designMode, and XUL textboxes.
Examples of appropriate bugs: After inserting a image, selecting Undo crashes Firefox; After deleting a word, the caret disappears.
The embedding API is the set of functions that an external application uses to host an instance of the layout engine within itself. The embedded layout engine provides services for rendering web content (HTML, XML, CSS, etc).
Any strangeness with keyboard typing, mouse actions, focus changes.
Component description needed.
For bugs in shared services/fxaccounts code related to Firefox accounts, used by B2G and Firefox.
The built-in profiler which can be used in order to get profiling information from within Gecko. Includes both the back-end and the front-end (Cleopatra).
For bugs in Core which do not fit into other more specific Core components
The geolocation API and framework enables reporting a physical
location, in cooperating with a location provider (such as a GPS).
qcms and other issues relating to Mozilla's color management
Mapping of cross platform rendering interfaces to various 2D graphics APIs
The graphics subsystem that implements hardware-accelerated (and software) composition of layers of content.
Text and font support in Gecko, including text shaping and font selection.
Bugs related to the integration of WebRender into Gecko.
For bugs in the Hardware Abstraction Layer (HAL) code regardless of the backend.
Example of appropriate bugs: implementation of a new feature for a backend, fixing a bug for a specific backend or general bugs regarding HAL.
This is the global history which tracks all URLs that a user has visited, across all sessions of the browser. This also includes the history window and link coloring. Examples of appropriate bugs: Chrome URLs incorrectly added to global history, Reproducible crash when sorting by Title in History window, misbehaviour in the History sidebar tab.
This component is for bugs with HTML form submission. For example, "hidden controls don't get submitted to the server".
This system consumes content from the web, parses, validates and builds a content model (document)
Persona / BrowserID Gecko and Firefox integration
For bugs about (un)blocking images from servers.
ImageLib decodes GIF, JPEG and PNG images, and provides the decoded data to the Compositor for display. If Firefox or Seamonkey can display an image when loaded separately from the page, ImageLib is working, and the actual imaging bug exists elsewhere within Firefox or Seamonkey.
Examples of appropriate bugs: PNG gAMA chunk ignored; Crashes on GIF w/corrupted frame(merr-01.gif); or PNGs and JPEGs aren't displayed on FreeBSD.
Internationalization is the process of designing and developing a software product to function in multiple locales. This process involves identifying the locales that must be supported, designing features which support those locales, and writing the code needed.
Core inter-process communication and IPDL system for communicating with and isolating sub-processes. Please file plugin-specific IPC bugs in Core: Plug-Ins and content-specific IPC bugs in Core: DOM: Content Processes.
File bugs here for issues involving the garbage collector (crashes, leaks, etc.), where the issue is not one caused by failure to use the JSAPI correctly.
File bugs here for issues related to anything exposed through the Intl property on the global object.
Covers keyboard shortcuts, access keys/accelerators, and navigation by using the keyboard (not the mouse or other input device).
Examples: Ctrl+W not closing the browser window under Windows. Command+N not
opening a new browser window under Mac OS. Alt+left arrow not going to the
under Linux. Alt not accessing the menu or access keys under Windows. Also, the
debate as to use Alt or Ctrl under linux as the keyboard accelerator key for
shortcuts. Requests for additional keyboard shortcuts.
For triage, reduction, and reassignment to other layout components.
Core layout and geometry for basic block and line elements. For example, margin collapsing bugs, border rendering bugs, and bugs with the inline box model belong here.
Issues with CSS floats or left/right aligned images. For example, bugs with the 'float' and 'clear' properties belong here.
For problems with HTML Form Elements: buttons, images, edit fields, passwords, file controls, submit buttons, selects, and textareas. NOT for file upload dialog problems, those belong in XP Toolkit/Widgets.
For rendering and layout issues with frames (<iframe>, <frame> and <frameset> elements in HTML).
Bugs related to the layout of images. Use ImageLib for issues with the decoding of images.
For code-level bugs in things like the pres shell, etc.
Relative, Absolute, and Fixed positioning, except when printing. If you don't know what this is then please don't move bugs here, instead select "Layout".
For bugs in the CSS and HTML table layout and rendering code. For example bugs with the HTML 'rules' attribute or the CSS 'border-collapse' property belong here.
For problems with enumerating and rendering system fonts, glyph substitution, fallbacks when specified font not available and legibility. Bugs with the CSS 'font' properties belong here.
Painting problems. If the object is in the right place, but doesn't paint correctly, it's a view system bug. If it paints OK, but in the wrong place, then it belongs in another Layout component. Bugs with the 'opacity', 'z-index', 'overflow', and 'clip' properties usually belong in this component. (In terms of code, this covers the view/ and gfx/src/nsBlender* directories.)
Construction of display lists, hit-testing, building of Layers and painting.
Localization is the process of adapting software for a specific international market; this process includes translating the user interface, resizing dialog boxes, replacing icons and other culturally sensitive graphics (if necessary) as well as customizing features.
For bugs related to the "mach" command-line tool.
Mathematical Markup Language
Most things related to memory allocation in Gecko, including jemalloc, replace-malloc, logalloc, etc.
File bugs here for headers, macros, data structures, methods, and other functionality which should be available to SpiderMonkey and to all Gecko code, implemented in the mfbt/ source directory.
For issues in the Android glue, the custom dynamic linker or other parts of the mozglue library.
JIT Compiler Infrastructure shared by Mozilla's TraceMonkey compiler and Adobe's Tamarin compiler.
For bugs in Mozilla's modular networking library (aka "Netlib" or "Necko".) The networking library supplies the software interface that Mozilla uses to access physical transports (e.g. the Internet and local drives), perform URL resolutions, and handle a variety of networking protocols.
Examples of appropriate bugs: URLs with backslash not fetched; URLs starting with a single slash turn into http:///; Cannot access authenticated FTP site.
For bugs in the cache, which stores recently accessed data for more rapid access. Includes the disk cache, memory cache, and all cache preferences.
Examples of appropriate bugs: Implement compression of network cache data; or Implement partial HTTP caching.
A general mechanism which server side connections (such as CGI scripts) can use to both store and retrieve information on the client side of the connection. This refers to HTML cookies; little blobs of data we store and share with sites
For bugs in Mozilla's implementation of DNS (Domain Name
For bugs in Mozilla's File IO code. This component deals with File specific issues like writing to disk, reading local files, etc Related problems with file:// protocol may also be addressed here.
For bugs in Mozilla's FTP code. This component deals with FTP specific issues like downloading, directory formats, problems with FTP login, or resuming partial downloads, etc.
Examples of appropriate bugs- Problems with multiple occurrences of files in directory listings, corruption in downloading certain files via FTP, etc.
For bugs in Mozilla's HTTP networking code. This component deals with HTTP specific issues like pipelining, keep-alive, HTTP proxies, 1.1 issues, redirects, authentication (basic), etc.
Examples of appropriate bugs: Problems with proxy authentication; HTTP redirects looping indefinitely, etc.
For bugs relating to the jar protocol handler, .jar file
handling, and .jar directory browsing.
For bugs in Mozilla's web sockets implementation, especially protocol and
network-related issues. Issues which are specific to the web sockets DOM
interface may be better classified as Core::DOM.
Covers issues relating to the asynchronous panning and zooming (APZ) module, including scrolling and gesture detection.
For bugs related to the permission manager but not the permission management.
Example of appropriate bugs: permissions in the database are ignored or removing permission doesn't work.
Example of inappropriate bugs: feature F should use permission P or any user interface related bugs.
Work items and bugs for the Platform Fuzzing Team
Bugs in core Mozilla code that supports registering and using plug-ins. For bugs in specific plugins, please file those bugs under External Software Affecting Firefox.
For bugs in libPref, the backend library that reads, parses, and writes preferences to the user's hard disk. Unless you're a Mozilla developer, your bug probably doesn't belong in this component.
Examples of appropriate bugs: prefs.js on the mac has non-mac style line endings; Large libpref string causes dialogs to crash on Linux; or JS Error at startup reading prefs file on migrated profile.
Problems in the rendering of Print Preview that are not seen when printing the same page.
Problems printing from this product should be submitted under this component.
Integration relating to the OS printing system, including cross-platform components such as the page setup dialog.
For bugs related to the QuickLaunch installer
option and preference, which keeps the application resident in memory after all windows are closed, to speed subsequent component loading.
Resource Description Framework: Core RDF components, including the in-memory datasource, composite datasource, RDF/XML parser, and RDF resource manager.
Features and bugs in the static analysis and rewriting tools used by Mozilla, including Elsa, Oink, and Dehydra.
For non-crypto security bugs. Or use this general component if you know you have a Browser security bug, but not sure what component to use. Bug will be reviewed for proper component.
Caps is the capabilities-based security system for the browser. Manages principals (entities responsible for a piece of code) and the protected capabilities (the ability to perform a restricted action) that may be enabled for given principals.
For process sandboxing bugs. Generally this covers code under the security/sandbox/ source directory, but there is code elsewhere to hook the different platform process sandboxes into Gecko etc.
A daemon that performs cryptographic operations on behalf of a client application.
Selection refers to the user action of selecting all or part of a document and highlighting the selected content.
Bugs involving conversion to html or plaintext, either during saving or during copy/paste. This component is NOT for general copy/paste bugs, for bugs involving save dialogs or writing to files when saving, or for I18n-related bugs; only for problems with the actual text which is saved.
For bugs with the spelling checker used by Mozilla-based applications. This includes the backend code, the Hunspell spell checker, the en-US Hunspell dictionary, and the osxspell interface to the Mac OS X spell checker.
The hierarchy of classes related to managing character sequences.
Bugs against the implementation of the Scalable Vector Graphics (SVG) specification. Reads and renders SVG content.
For newly filed bugs that need some help finding the right place to go.
Bugs and enhancement requests relating to the Web Audio support.
For problems in using SOAP
to call Web Services from
scripts in Mozilla.
Examples: WSDL crashes if no <message> defined; WSDL Proxy callback doesn't allow access to the SOAP Response; Need better facilities to debug SOAP calls.
General bugs associated with WebRTC
Bugs in WebRTC audio and video capture, handling, echo cancellation, encoding, and playback
Bugs in the networking portions of WebRTC (PeerConnection dataChannels, SCTP, DTLS, SRTP, ICE, TURN, STUN, etc)
Bugs in WebRTC call-setup and re-negotiation code, in particular JSEP and SDP handling
Cross platform widget interfaces and cross platform base implementations. Bugs that belong in this component are cross-platform problems and API
issues. Bugs like this that only occur on one platform belong in the appropriate component listed below.
Mapping of cross platform widget interfaces to Android platform APIs.
Mapping of cross platform widget interfaces to Mac Cocoa APIs.
Mapping of cross platform widget interfaces to Gonk
Mapping of cross platform widget interfaces to GTK platform APIs (both versions).
Mapping of cross platform widget interfaces to Win32 platform APIs.
Mapping of cross platform widget interfaces to WinRT platform APIs
X-Remote Client and Server
The Extensible Binding Language, used to bind new behavior and new content to XUL and HTML elements.
For bugs in our XML handling. For example, parser errors, or errors in wellformedness error reporting.
For bugs in the cross-platform menu infrastructure, including the display and behavior of pop-up menus, pull-down menus, and context menus. (Pop-up menus that are part of a web page's content should be assigned to HTML Form Controls.)
Examples of appropriate bugs: Command key symbol is missing from Mac menus; or Context menus pop up in wrong location.
For bugs in the XUL
language. (XUL is an XML-based language which specifies Mozilla's user interface.)
If you're not actually writing XUL code, this is probably not the right place for your bug.
Examples of appropriate bugs: Duplicate window ID causes infinite loop; or Scrollbars disappear after loading XUL document
This is the basis of our component technology; this covers the mozilla/xpcom source directory and includes the "repository". Unlikely a tester would be able to tell there was an XPCOM problem specifically.
For bugs on Mozilla's XSLT support. See the project
for tips on testcases and commonly encountered legacy problems.
XPToolkit includes a User Interface (UI) widget set
consisting of menu bars and menus, toolbars and toolboxes, titled buttons, trees, tab widgets, scrollbars, splitters, progress meters, and boxes. Use this
category for file picker, color picker, font picker and dialog/window bugs, too. XP Toolkit also accepts bugs relating to copy/paste, drag & drop, key bindings, the
clipboard, and focus issues. All bugs concerning skins should use the "Skinability" component.
User interface widgets that are part of a web browser's content (such as web forms) are actually handled by a separate toolbox --- rather than XP Toolkit --- and should be assigned to HTML Form Controls.
Examples of appropriate bugs: Scroll bar disappears when you shrink window; Mouse wheel scrolling broken under Linux; or Horizontal scroll bar flickers mid-screen during window resize.
NOTE: Please use "Keyboard Navigation" component for key cmd problems.