Help pinpoint a bug

Firefox updates sometimes break Paxmod. The first to notice that will usually be Nightly users because they get an update every day, even if no new Firefox version was officially released. Reporting those bugs here is already great. But if you got extra time, you can help even more by finding out which exact Nightly version introduced the bug.

Such a "bisection" can be done without the need for particular tech skills - here are some hints:

• Nightly versions for any date are available at https://ftp.mozilla.org/pub/firefox/nightly/.

• Go into the *-mozilla-central directory for a specific date (e.g. https://ftp.mozilla.org/pub/firefox/nightly/2022/08/2022-08-01-21-51-29-mozilla-central/) and choose the right build your platform. If you're a Windows user, you likely want the firefox-*.*.en-US.win64.zip file. You can then just extract it and run the firefox.exe from that folder without installation. Download the .zip rather than any installer.exe since constant installing and uninstalling to test out different versions is pretty cumbersome.

• Notice that builds from different dates may have the same version number in the filename (firefox-105.0a1....), but they are not the same. If you don't remember which date's Nightly build you're running you can look up the build ID on about:support.

• On Linux, an easier way to download versions for specific dates is via the fuzzfetch tool.

If you now can tell at which exact Nightly version (date) your bug first appeared, you're making a fix so much easier because there's only a day worth of code changes to look through in order to find what caused it. This wouldn't be possible between official releases due to the amount of code.