{"id":13528113,"url":"https://github.com/webcompat/web-bugs","last_synced_at":"2025-04-01T11:30:58.542Z","repository":{"id":15186634,"uuid":"17914657","full_name":"webcompat/web-bugs","owner":"webcompat","description":"A place to report bugs on websites.","archived":false,"fork":false,"pushed_at":"2023-06-24T06:09:29.000Z","size":361,"stargazers_count":747,"open_issues_count":2021,"forks_count":68,"subscribers_count":84,"default_branch":"master","last_synced_at":"2024-11-25T08:45:13.463Z","etag":null,"topics":["webcompat"],"latest_commit_sha":null,"homepage":"https://webcompat.com","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/webcompat.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2014-03-19T18:00:24.000Z","updated_at":"2024-11-13T11:12:46.000Z","dependencies_parsed_at":"2024-01-08T07:59:58.793Z","dependency_job_id":null,"html_url":"https://github.com/webcompat/web-bugs","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webcompat%2Fweb-bugs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webcompat%2Fweb-bugs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webcompat%2Fweb-bugs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/webcompat%2Fweb-bugs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/webcompat","download_url":"https://codeload.github.com/webcompat/web-bugs/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":246631676,"owners_count":20808732,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["webcompat"],"created_at":"2024-08-01T06:02:13.236Z","updated_at":"2025-04-01T11:30:58.197Z","avatar_url":"https://github.com/webcompat.png","language":null,"funding_links":[],"categories":["Others"],"sub_categories":[],"readme":"web-bugs\n========\n\nA repo used by the Web Compatibility community to track issues reported via [webcompat.com](http://webcompat.com)\n\n![Screenshot of webcompat.com](screenie.png)\n\n\n### Labels\nLabels are used for helping to filter bugs into groups but also to track the status of the bug. Here’s what each label means:\n\n- `browser-xyz` - The bug exists in *xyz* browser\n- `ios` - The bug exists in an iOS browser\n- `mobile` - The bug exists on mobile devices\n- `nsfw` - The website has content that could be considered offensive\n- `os-android` - The bug exists in an Android browser\n- `windows` - The bug exists in a Windows browser\n\n##### Open Statuses\nStatus 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.\n- `status-needstriage` - The issue needs to be screened and prioritized\n- `status-needsdiagnosis` - Issue needs further analysis to find the cause\n- `status-needscontact` - The issue has been analyzed, a contact for the site is required\n- `status-contactready` - A contact has been found, it is ready for someone to contact the site\n- `status-sitewait` - The web site with the issue has been contacted\n- `status-needsinfo` - Issue needs more information, usually means process is blocked until info is provided.\n- `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.\n\n##### Closed Statuses\nStatus labels which should only be used when a bug report is closed.\n- `status-duplicate` - Issue is the same as an already-reported issue\n- `status-fixed` - Issue is fixed\n- `status-incomplete` - The report requires more information to be actionable\n- `status-invalid` - Issue is not a web compatibility issue\n- `status-wontfix` - The issue will not be fixed\n- `status-worksforme` - The issue can't be reproduced\n\n### Best practices\n\nIf 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?\n\n#### Filing web compatibility bugs\n- Fill the bug report form out completely. The more information you provide the easier it is for volunteers to understand the problem\n- List any other browsers you tested the site with\n- Try to avoid reporting issues for sites that are broken in all browsers. We like to focus our energy on sites that work in one browser but not others\n- If you feel comfortable dig in and analyze the bug as well\n\n#### Analyzing web compatibility bugs\n- Confirm that you can reproduce the error. Ideally you should use a clean browser profile. See [this tutorial for Firefox](http://www.otsukare.info/2014/11/12/configure-webcompat-browser).\n- Set any related labels - if the bug appears on Chrome for Android, set the “browser-chrome” and “os-android” labels\n- Provide details on which piece of code is broken\n- List out any relevant error codes\n- If possible, suggest a way to fix the code to work in all browsers\n- Once complete, add the “status-contactready” label\n- If you feel comfortable find a contact at the site and reach out\n\n#### Contacting the site/company\n- Once a bug is set to “status-contactready” the site can be contacted\n- After you have attempted to make contact remove the \"status-contactready\" label and add \"status-sitewait\" so others don't attempt to contact\n- Leave details about who you are contacting, example “Joe Webmaster - Developer at Company X”\n- Be careful not to leak any private information like email addresses, phone numbers\n- If you post somewhere public like twitter, include the link to the tweet in the bug for easy tracking\n- If you receive an issue tracking number from the site include this in the bug\n- When you receive responses, leave some information on the bug (paraphrasing is fine)\n- If no response is received after a week or two, try another method. After a month or three contact attempts we can stop and revisit it later\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwebcompat%2Fweb-bugs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fwebcompat%2Fweb-bugs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwebcompat%2Fweb-bugs/lists"}