Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

FF removes multiple spaces from file name on file download

bk3963
bk3963
more options

When I download a file with multiple spaces in the name, like 'test space.txt' (there are 2 spaces between test and space), FF condenses the extra space into one, like 'test space.txt' (there is only 1 space between test and space). This happens on multiple websites and does not occur in other browsers.

When I download a file with multiple spaces in the name, like 'test space.txt' (there are 2 spaces between test and space), FF condenses the extra space into one, like 'test space.txt' (there is only 1 space between test and space). This happens on multiple websites and does not occur in other browsers.

All Replies (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

It sounds as though it must be intentional. Is there a reason to preserve extra whitespace in the file name? If this is causing a problem, you could file a bug: https://bugzilla.mozilla.org/

By the way, since your Firefox reported itself to be version 78:

If you are using the Extended Support Release of Firefox 78, I suggest testing in the current Firefox Nightly, which likely will be the base for the next ESR. Issues unique to Firefox 78 are unlikely to get attention, so it would make more sense to file the bug against Nightly.

On the other hand, if this identification results from running Firefox 89 with privacy.resistFingerprinting enabled, you can ignore the above comment.