34
edits
Compatibility/Guide: Difference between revisions
Jump to navigation
Jump to search
→Analyzing for Web Compatibility Issues: add description of triage-diagnosis and link to triage process
(→Reporting a Web compatibility issue: Add link to webcompat reporter add-on.) |
Astevenson (talk | contribs) (→Analyzing for Web Compatibility Issues: add description of triage-diagnosis and link to triage process) |
||
| Line 48: | Line 48: | ||
== Analyzing for Web Compatibility Issues == | == Analyzing for Web Compatibility Issues == | ||
There are many ways of | Analysis is broken down into two processes: triage and diagnosis. | ||
The [[Compatibility/Guide/Triage|triage process]] involves testing the reported issue to validate if the issue: | |||
* Can be reproduced | |||
* Is considered a valid Web Compatibility bug | |||
* Has been reported previously (a duplicate) | |||
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 Process for Analysis === | === Mozilla Bugzilla Process for Analysis === | ||