22 Apr 2014

For the past couple of months—together with Alexa Roman and the rest of the MozWebCompat crew—I’ve been working on getting to something much closer to a hyperlinkable state. Today I think it’s probably good enough to remove the lame “coming soon” page (designed by yours truly; apologies) that used to exist and ship.

So how does this work?

1) Internet 2) Site/app/lib/whatever works in cool-guy browser A but not cool-guy browser B 3) Get a little emotional, it’s okay 4) Report an issue at

You can report with your GitHub credentials if you’re into that, or if the required “public_repo” OAuth scope freaks you out you can report anonymously via one of our sweet GitHub proxy bots.

At this point, (in theory) someone will be able to diagnose what’s going on and reach out to the site to advocate a fix or submit a patch, etc. If it’s browser bug territory we want be able to upstream issues to a browser vendor bug tracker (see issue #84).

Right now all issues are collected in a “web-bugs” GitHub repo: but we’ll soon be working on displaying those on itself to make it easier to understand what issues have been reported for which domains or browsers, etc.

So. If any of that was remotely interesting to you, and if you’re into open source, Python, HTML, CSS, JS, or whatever, there’s work to be done.

Happy bug reporting.


FAQZO (Frequently Asked Questions by Zach (Once))

Q: Is the target market newbies that are afraid of bugzillas?

A: Yeah, in part. Browser bug trackers can be confusing. Or they require a new account. Or they can feel like black holes.

Q: Or lazy people?

A: Yeah, why not.

Q: Both?

A: OK, Sure.

Q: Can I just cc stuff from twitter?

A: If by “cc stuff from twitter” you mean create a meaningful report that links to a tweet, absolutely. We could probably do some sweet Twitter integration or whatever too.