AFAICS, every Firefox build for F32 or Rawhide since firefox-72.0.2-3.fc32 has failed. So that's still the version F32 (and Rawhide) are stuck on.
We have the Beta release upcoming, so this is both a bad look and a practical issue, as there were security fixes in 73.0 that we're missing.
I'm proposing this as a Beta freeze exception: if we can get a build through before Beta, and it tests out okay, I think we should include it in the Beta so we don't look bad and potentially leave Beta users using a less-than-perfectly-secure browser to access the internet. That's the purpose of this bug - it's not a bug *for* any one specific build failure, it's a freeze exception bug for 'getting a newer Firefox build in the Beta if we can'.
Firefox 74 is going to be released on 2020-03-10 and we work on the builds now (https://koji.fedoraproject.org/koji/buildinfo?buildID=1473376).
But that builds will use in-tree nss as we're missing up-to-date nss for Fedora 32 (https://bugzilla.mozilla.org/show_bug.cgi?id=1615557).
(In reply to Martin Stransky from comment #1)
> But that builds will use in-tree nss as we're missing up-to-date nss for
> Fedora 32 (https://bugzilla.mozilla.org/show_bug.cgi?id=1615557).
Btw. That bug was posted to me by Daiki (nss maintainer), I'm not sure how is that related to Fedora 32 nss builds.
Ahh, I see that nss team manage to build nss 3.50 for rawhide:
so there's a chance to have nss for other fedoras soon.
https://koji.fedoraproject.org/koji/taskinfo?taskID=42179399 is coming.
FEDORA-2020-0db6047b9e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0db6047b9e
Discussed during the 2020-03-09 blocker review meeting: 
The decision to classify this bug as an "AcceptedFreezeException" was made as it is a noticeable issue that cannot be fixed with an update.
firefox-74.0-1.nss.fc32 has been pushed to the Fedora 32 stable repository. If problems still persist, please make note of it in this bug report.