Invalid Bugs

Why was my bug closed as invalid?

Sometimes users report bugs on webcompat.com and they get closed as invalid. This doesn't necessarily mean the site doesn't have a bug, but it isn't considered a web compatibility bug.

If you feel your bug should be considered valid after it has been closed, just leave a comment. Sometimes we make mistakes when triaging.

Common reasons:

• Lack of actionable information: If a bug contains no reliable steps to reproduce, or a screenshot that clearly displays the problem an issue may be close as invalid.

• Reproducible everywhere: If an issue is the same in all browsers. This is not a Web Compatibility issue.

• Tracking Protection / Ads Blocker / Cookies blocker: All of these are not Web Compatibility issues because the site is working correctly without them, in one or all browsers. These are choices that users have made that can affect how pages render or function.

• Fake profile/Abusive behaviors: A site which is being abusive, is a scam, or contains a fake profile are not web compatibility issues. There are no differences in between browsers. These issues are better reported directly to the site.

• No Mobile site: When the site doesn't provide a mobile version for any browser, then it's probably not a Web Compatibility issue. It just means they only provide a version optimized for Desktop.

• Flash Required: A Web site that requires Flash in every browser for having a satisfying user experience is not a Web Compatibility issue. But a Web site which is for example providing a working video in Browser A without Flash and requires Flash for another Browser B with the same capabilities is a Web Compatibility issue.