Needs Diagnosis Queues by Team

• Web Compat
• DOM
• DOM Storage
• Graphics
• Javascript
• Layout
• Media
• Networking
• Privacy
• Video Conferencing
• Unset P1/P2

Diagnosis Process

Document your diagnosis

During diagnosis document whatever progress you made. This will help anyone else looking at the bug to pick up where you left off.

If you get stuck and need help from the webcompat team, set diagnosis-team: webcompat in the User Story field. If you think the issue is in another component you may set that component directly in the user story (using the site issue triage addon is recommended to get the data format correct).

Diagnosis Done?

Once you understand the root cause of the issue:

• Remove the webcompat:needs-diagnosis keyword to indicate that diagnosis is complete
• If the root cause is a platform bug, set the webcompat:platform-bug keyword, and set the site report bug to depend on the platform bug(s) that cause the issue. These bugs should also have the webcompat:platform-bug keywords set.
• If the root cause is a problem with the site (e.g. sending incorrect code to Firefox) then set either webcompat:needs-contact or webcompat:contact-ready keywords depending on whether we have an existing relationship with the site.
• If the problem might have a workaround (e.g. spoofing as another browser, or changing some CSS) set webcompat:needs-sitepatch.
• If the problem is an area where the spec is ambiguous, and the site depends on a specific behavior, or where Gecko is following the spec but other browsers are not, or some similar case where a Gecko bug might be marked as WONTFIX, file an issue in Web Compatibility :: Knowledge Base describing the problem, and linking to any spec issues, or issues on other browsers, and set the site report bug to depend on this knowledge base bug.