Thomas Skyttegaard Hansen

The problem is gone in the nightly build after the release of Firefox 87.0, so it was a bug in Firefox, which fortunately has been fixed now.

Yes, the problem is in 87.0, but has disappeared in the build after 87.0. That was what I was trying to say 😉. So I guess and hope we won't...