A repo used by the Web Compatibility community to track issues reported via webcompat.com
Labels are used for helping to filter bugs into groups but also to track the status of the bug. Here’s what each label means:
browser-xyz
- The bug exists in xyz browserios
- The bug exists in an iOS browsermobile
- The bug exists on mobile devicesnsfw
- The website has content that could be considered offensiveos-android
- The bug exists in an Android browserwindows
- The bug exists in a Windows browserStatus labels which should only be used when a bug report is still open. These are in the order the bug process should typically follow, with the exception of needsinfo and leaveopen.
status-needstriage
- The issue needs to be screened and prioritizedstatus-needsdiagnosis
- Issue needs further analysis to find the causestatus-needscontact
- The issue has been analyzed, a contact for the site is requiredstatus-contactready
- A contact has been found, it is ready for someone to contact the sitestatus-sitewait
- The web site with the issue has been contactedstatus-needsinfo
- Issue needs more information, usually means process is blocked until info is provided.status-leave-open
- The issue has been analyzed, and for some reason it was decided that this issue needs to remain open. The person who labeled it this way, will handle it further.Status labels which should only be used when a bug report is closed.
status-duplicate
- Issue is the same as an already-reported issuestatus-fixed
- Issue is fixedstatus-incomplete
- The report requires more information to be actionablestatus-invalid
- Issue is not a web compatibility issuestatus-wontfix
- The issue will not be fixedstatus-worksforme
- The issue can't be reproducedIf you’re using Webcompat.com already, you’re probably pretty awesome. So why do you need to read this? Well from experience we know a few tricks that make the web compatibility process go even smoother. And who doesn’t want to learn sweet new tricks?