If it's such an easy fix, then fix it. If it's a js/css/html/xul-only fix (and chances are good it is, when it's a usability issue, as the frontend/UI code js

If it's such an easy fix, then fix it. If it's a js/css/html/xul-only fix (and chances are good it is, when it's a usability issue, as the frontend/UI code js on a high level), then you do not even have to really build Firefox but can use artifacts mode[1], which takes a few minutes for the initial build and only a few seconds for subsequent builds. Then find a reviewer. I usually look at the recent activity of files I touch (or related files, or related bugs), find functional changes and just add whoever reviewed those most recent changes. Even easier when it's regressions, then you can see who reviewed the regressed changeset and who wrote it and CC them as well. If the person(s) you picked do not want to review it or cannot review it, they will tell you, and usually suggest who else to ask. If this doesn't work, then you can always ask/nag on IRC. [1] https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g...