Do not forget: '''Be nice'''. It is our collective effort.
== Analyzing for Diagnose a Web Compatibility Issues Issue ==
Analysis is broken down into two processes: triage and diagnosis.
There are many ways of diagnosing a web site for Web Compatibility issues. We could write an entire book with the types of issues and techniques used to find them.
=== Mozilla Bugzilla Diagnosis Process for Analysis and Tools ===
You might want help analyzing [https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Mobile&resolution=---&list_id=7757638 Mobile Web Compatibility bugs]. A bug which has the status '''NEW''' or '''ASSIGNED''' are basically the same. # When analyzing the bug, take it (and change the bug to '''ASSIGNED''').# Once you've discovered the type of issue affecting the site:## document in a comment## flag it with The work is based on a whiteboard keyword for example [serversniff] if it's related to server side user agent detection. [[Compatibility/BugsGuide#whiteboard_keywords_for_categorizing_the_issues Diagnosis| Jump to the full listdiagnosis process]].# If you do not plan You may want to work further read this. It gives useful hints on how to organize the bug, such as contacting the Web site, '''Unassign yourself''' You may use work. [[Compatibility/Tools|some tools and techniques]] for investigating bugshave also been described.
== Finding The Right Contact on a Web site ==
