Important links

Chromium:

• Report bugs at http://code.google.com/p/chromium/issues/entry
  
• View existing bugs at http://code.google.com/p/chromium/issues/list
  
• Bug Reporting Guidelines for the Mac & Linux builds (with links to known issues pages)

Chromium OS:

• Report bugs at http://code.google.com/p/chromium-os/issues/entry
  
• View existing bugs at http://code.google.com/p/chromium-os/issues/list

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 the bug is a compatibility bug, provide a URL to replicate the issue.
• 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.
• Before reporting a crash bug, please read these guidelines about reporting crash bugs.
• Additional Bug Reporting Guidlines for the Mac & Linux builds.

Labels

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.

Status

Open bugs

Status value	Description
Unconfirmed	The default for public bugs. Waiting for someone to validate, reproduce, or otherwise confirm that this is a bug.
Untriaged	A confirmed bug that has not been reviewed for priority or assignment. This is the default for project members' new bugs.
Available	Confirmed and triaged, but not assigned. Feel free to take these bugs!
Assigned	In someone's work queue.
Started	Actively being worked on.

Closed bugs

Status value	Description
Fixed	Fixed.
Verified	The fix has been verified by test or by the original reporter.
Duplicate	This issue has been reported in another bug. A comment should be added when a bug is closed as Duplicate, containing the active bug ID for this issue.
WontFix	Covers all the reasons we chose to close the bug without taking action (can't repro, working as intended, obsolete).
Upstream	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).
FixUnreleased	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.
Invalid	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

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.