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.
Bugs with the HTML5 <canvas> element, its XUL sibling, and related rendering contexts.
Bugs with the WebGL Canvas Context.
Issues with loading CSS style sheets from the network, parsing style sheets and style attributes in HTML markup, performing the CSS cascade, selector matching, and producing correct computed values for CSS properties.
- toggling class name on an element does not restyle the element
- background-color property does not support hsl() values
- CSS Cascading
- CSS Conditional
- CSS Logical Properties
- CSS Namespaces
- CSS Scoping
- CSS Style Attributes
- CSS Syntax
- CSS Values
- CSS Variables
- Media Queries
Issues with animating and transitioning CSS properties. For issues with the Web Animations API, see the DOM: Animations component.
- transitions are not triggered when the display property is changed simultaneously
- the font-weight property animates discretely but should be interpolated smoothly
- CSS Animations
- CSS Timing
- CSS Transitions
- Motion Path
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.
This component covers the Web Animations implementation in Gecko.
Issues with code implementing WebIDL, not WebIDL itself
Issues related to implementation of content processes in B2G and Firefox, especially the code in dom/ipc (more info)
Issues with CSSOM support and other CSS-related DOM APIs. This is not the place for most CSS bugs unless they involve scripting; see the CSS and Layout components instead.
- document.styleSheets doesn’t include style sheets from file:// URLs
- crash setting element.style.color to "red"
- CSS Font Loading
- CSSOM View Module
- Geometry Interfaces
This component covers APIs 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.
For bugs in the DOM Blob, DOM File and FileSystem APIs
This component covers the IndexedDB implementation in Gecko.
Networking-related DOM APIs, such as XmlHttpRequest, Fetch, Web Sockets, EventSource, and Beacon.
Push Notifications wake up and notify web-apps when a remote server has something of interest for the web-app.
Longer description: For bugs in Gecko's centralized management of storage and disk usage quota in user profiles.
Native content-based security features including: Content Security Policy (CSP), Mixed Content Blocker (MCB), and Safe Browsing.
This component covers the Service Worker implementation in Gecko.
This component covers the LocalStorage and SessionStorage implementation in Gecko
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.
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 implementation.
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.
Issues with glyph rasterization and painting, font format support, and interfacing with platform font APIs. For issues with font selection, text shaping, and glyph selection, see the Layout: Text and Fonts component.
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 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.
Bugs relating to the integration of Microsoft Distributed COM into Gecko
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.
Implementation of the WebAssembly standard, including compilation and runtime support
Issues in Layout that do not fit into any other Layout component or which span multiple Layout components.
Bugs related to the top level presentation objects (pres shell, pres context, and document viewer), the frame constructor, and the base frame classes, as well as general issues with alignment and sizing, all belong here.
Issues with core layout and geometry for basic block and inline elements. This includes issues with ::first-letter and ::first-line.
- margins between two blocks do not collapse properly
- button does not align its baseline correctly with the rest of the line it’s in
- CSS Box
- CSS Inline Layout
Issues with CSS multi-column layout.
- column rules are not properly drawn on overflow columns
- column gap should be included in minimum width calculation when the number of columns is non-auto
- CSS Multicol
Issues with CSS flexible box layout.
- flex items not wrapping in multi-line flexbox with "overflow:hidden"
- baseline for empty flexbox container seems wrong
- CSS Flexbox
Issues with CSS floats and clearance.
- float moves to wrong position when you dynamically set "clear" property on ancestor
- inline frames without enough inline space should clear floats, regardless of shape-outside
- CSS 2.2 (§ Floats, and others)
- CSS Shapes
Issues with the layout and appearance of HTML form controls, such as buttons, date/time pickers, select elements, and textareas.
- datepicker remains visible after tabbing out of date input field
- the filename field of <input type=file> renders incorrectly in vertical writing mode with dir=rtl
- HTML (§ Forms)
Issues with handling of CSS generated content, list items, and counters.
- ::before and ::after are not rendered correctly on <details>
- list item bullet characters don't display in the specified font face
- CSS Counter Styles
- CSS Generated Content
- CSS Lists
- CSS Pseudo-Elements
Issues with CSS grid layout.
- stretching the inline size of <button> grid items doesn't work
- abspos child of a grid should respect "align-self"/"justify-self" when computing its static position
- CSS Grid Layout
Issues with the CSS images and other replaced content. This includes loading, layout, and rendering of CSS images (such as in background-image), and the layout of HTML img, picture, video, iframe, frame, and frameset elements. For issues with image decoding and video playback, see the ImageLib and Audio/Video components respectively.
- SVG as image with an intrinsic width and max-height has its width incorrectly scaled down by the same ratio as the height is scaled down
- <iframe> has incorrect default size in vertical writing mode
- CSS Backgrounds
- CSS Images
Issues with relative, absolute, fixed, and sticky positioning.
- <thead> with position: sticky gets stuck after scrolling down
- wrong absolute positioning when the containing block has a min-height and overflow:hidden
- CSS Positioned Layout
Issues with CSS Ruby text layout.
- ruby annotation is not placed correctly for RTL content
- ruby base after a line break may disappear
- CSS Ruby
Issues with the layout and rendering of scrollable elements, scrollbars, and with the handling of overflowing content. Also includes issues with rendering of the regular text caret and the accessible caret. For problems with rendering of currently scrolling elements, see the Panning and Zooming component.
- <legend> w/ display:flex overflow:scroll sometimes renders without scrollbars
- overflow: hidden on fieldsets spills over
- CSS Scroll Anchoring
- CSS Scroll Snap
- CSS Scrollbars
- CSS Overflow
Issues with table layout and rendering.
- border-style: groove not applied for tables with border-collapse: collapse
- incorrect width for table cells with padding, box-sizing: border-box, and table-layout: fixed
- CSS 2.2 (§ Tables)
Issues with CSS font selection, font loading, text shaping and glyph selection, breaking, text decorations, bidirectional text processing, and white space processing. For issues with glyph rendering and font format support, see the Graphics: Text component.
- line-breaking code does not handle supplementary-plane characters properly
- double or wavy decoration lines are not repainted correctly if specified on floating first letter
- CSS Fonts
- CSS Size Adjustment
- CSS Text
- CSS Text Decoration
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.
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.
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 Service)
Requests for changes to the Public Suffix List
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.
Bugs related to the performance/correctness of the on-the-wire WebSocket networking protocol: file other WebSockets bugs under DOM:WebSockets interface may be better classified as Core::DOM.
Covers issues relating to the asynchronous panning and zooming (APZ) module, including scrolling and gesture detection.
Performance work items and bugs requiring action by the Firefox Performance team
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.
Issues with layout and rendering a document in Print Preview mode. For problems in printed or PDF output that do not appear in Print Preview, see the Printing: Output component.
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 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.
- OneCRL (certificate revocation) - Intermediate certs list for AIA chasing solution (certificate whitelist and preload lists) - List of CRLs for end-entity certs - HSTS preloads - white-list of accepted intermediate certs
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.
Issues with the layout or rendering of SVG content and interacting with the SVG DOM.
- SVG marker can not be clipped with clip-path
- x position adjustments of SVG vertical text on a path moves in the wrong direction
For newly filed bugs that need some help finding the right place to go.
Bugs and enhancement requests relating to the Web Audio support.
Construction of display lists, hit-testing, building of Layers and painting.
For bugs related to the Web Replay technology used when recording, replaying, and rewinding tabs
This component covers the Web Speech API implementation in Gecko.
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
Bugs with the WebVR functionality, including devices, graphics and integration
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 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
Creation and management of top-level windows
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 Layout: Form Controls.)
Examples of appropriate bugs: Command key symbol is missing from Mac menus; or Context menus pop up in wrong location.
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 page for tips on testcases and commonly encountered legacy problems.
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