Chromium (the web browser)
Chromium OS (the operating system)
You need a Google Account
associated with your email address in order to use the bug system.
Bug reporting guidelines
- Make sure the bug is verified with the latest Chromium build.
- If it's one of the following bug types, please provide some further information:
- Provide a high-level problem description.
- Mention detailed steps to replicate the issue.
- Include the expected behavior.
- Verify the bug in other browsers and provide the information.
- Include screenshots, if they might help.
- If a bug can be reduced to a simplified test, then create a simplified test and attach it to the bug.
- Additional Bug Reporting Guidlines for the Mac & Linux builds.
- Additional Guidelines for Reporting Security Bugs.
Release block guidelines
Labels are used to help the engineering team categorize and prioritize the bug reports that are coming in. Each report can (and should) have multiple labels.
For details on labels used by the Chromium project, see Chromium Bug Labels.
||The default for public bugs. Waiting for someone to validate,
reproduce, or otherwise confirm that this is a bug.
||A confirmed bug that has not been reviewed for priority or assignment. This is the default for project members' new bugs.
||Confirmed and triaged, but not assigned. Feel free to take these bugs!
||In someone's work queue.
||Actively being worked on.
||The fix has been verified by test or by the original reporter.
This issue has been reported in another bug, or shares the same root cause as another bug. When Duplicate is selected, a field will appear for the ID of the other bug --- be sure to fill this in.
Mark the bug with less information/discussion in it as the Duplicate.
||Covers all the reasons we chose to close the bug without taking action (can't repro, working as intended, obsolete).
||Bugs that turn out to be in another project's code and that we've filed with that other project. Useful for tracking known issues that manifest themselves in our product, but that need to be fixed elsewhere (such as WebKit and V8 issues).
||A special state for security hotfixes to mark bugs that are fixed, but not yet delivered to users. Bugs with this status will be visible only to project members and the original reporter.
||Illegible, spam, etc.
Bug life cycle
- When a bug is first logged, it is given Unconfirmed status.
- The status is changed from unconfirmed to Untriaged once it has been verified as either a Chromium or a WebKit bug.
- A bug that appears in Chromium as well as Safari is a WebKit bug and should be reported to bugs.webkit.org.
- A bug that appears only in Chromium is a Chromium bug.
- Once a bug has been picked up by a developer, it is marked as Assigned.
- A status of Started means a fix is being worked on.
Deciding where to submit your bug
Usually, Chromium-related bugs should be filed under one of the following projects:
Filing bugs that you find in Chromium OS
If you can reproduce the bug in Chromium for Linux, file the bug under chromium
. If you can't reproduce it, file it under chromium-os
Filing Chromium bugs at bugs.webkit.org
If a Chromium bug turns out to actually be a bug in WebKit, then use the following steps in deciding whether to file the bug at bugs.webkit.org.
- Make sure to test the behavior in the latest WebKit nightly, Firefox, Chromium, Internet Explorer and Opera browsers.
- If the bug does not happen in a WebKit nightly, but does happen in Chromium, then do not file the bug to webkit.org.
- If any two of Firefox, Internet Explorer and/or Opera have the same behavior that is different from WebKit/Chromium, then file the bug at webkit.org.
- If the intended behavior works in only one of Firefox, Internet Explorer or Opera or if every browser does something different, then apply the label "NeedsEngReview" so that a Chromium engineer can review the bug before taking further steps.