(In reply to Troels Liebe Bentsen from comment #4)
> There is also a bit of discussion on changing the behaviour of fscrypt to use EXDEV instead:
>
> https://github.com/google/fscrypt/issues/124
>
> But why is Firefox using the /tmp folder in the first place, would it not be better to do a tmp file in the same folder to start with and then maybe fall back to /tmp if that fails?
This would probably be better, yes. Both for privacy (if you're downloading to an encrypted folder, there is probably a good reason) and for performance (renaming across file systems is slow).
(In reply to Troels Liebe Bentsen from comment #4)
> There is also a bit of discussion on changing the behaviour of fscrypt to use EXDEV instead: /github. com/google/ fscrypt/ issues/ 124
>
> https:/
>
> But why is Firefox using the /tmp folder in the first place, would it not be better to do a tmp file in the same folder to start with and then maybe fall back to /tmp if that fails?
This would probably be better, yes. Both for privacy (if you're downloading to an encrypted folder, there is probably a good reason) and for performance (renaming across file systems is slow).