It seems that FizillaCFM is shortening a filename upon download based on the length a file is allowed to have in MacOS versions prior to X. There should be a check to see if the carbonized app is running in OS X or MacOS < X and base the decision to truncate on the results of this test. This bug could be severe, as OS X depends on the extensions of some files to determine file-type (pdf, .sit.bin, etc.) - w/ the end of the file truncated, a user may save a file that the OS cannot decode subsequently (no file extension).

->apps

You mean saving long filenames into HFS (31 characters) right? I think we would also need a check for FS type.

I believe it is HFS+ - command-I on 'Macintosh HD' indicates "MacOS Extended", which I believe is HFS+. In any case, downloading a file via ncftp results in no truncation of the name and downloading a file via IE 5.1 results in no truncation of the name ... so, apparently the FS is capable, Moz is just not allowing it.

->sdagley for Mac OS X triage

Reporter, can you provide precise instructions on how to reproduce this bug? It should include descriptions of what you expect to see and what you actually see. Also, can you provide a link to a smaller file? (The URL you provide is to a huge file.) There does seem to be a problem with long filenames in the Save dialog under OS X 10.1, but it exists in all applications, including the Finder. (You can't type in more than 31 characters in that dialog, which is stupid, but the OS's fault and not Mozilla's.)

Here's a link to a directory with a 0k file on my server that exceeds 31 characters: http://www.projkts.net/mozilla-test/ I tried saving this file from IE 5.1 and found that it is now also truncating the filename (this didn't used to be the case, if I recall correctly). I'm running OS X, 10.1 now, so maybe the Carbon layer is doing something different now. Is Moz doing anything to truncate the filename or is it leaving it entirely up to the OS? Also - I was able to rename an existing file in the Finder and give it a name that exceeded 31 characters, no problem. -Brice

Did apple ever extend the permissible file length maximum? The extensions to HFS mostly improved the data structures (variable size allocation blocks and increased total volume capacity). If this happens in other apps, then "not our fault."

The attachment I just created shows the file that I downloaded from my server via ncftp - it had no problem saving a file whose name exceeds 31 characters. I'm desperately searching for a GUI app that allows this, but I have yet to come up with anything (IE apparently doesn't anymore!!) If there is truly no workaround for this issue (I certainly hope this is not the case) shouldn't Moz at least try to shorten the name semi-intelligently? Don't know how doable this is ... how is it done on other platforms?

each application needs to be updated to the HFS+ apis to get long file names. mozilla has not yet gone there. I'm betting IE hasn't either.

Is there already an open bug about HFS+, Mike?

Yepperoonie, it's a dupe *** This bug has been marked as a duplicate of 89064 ***

verified dup.

how hard would it be for me to select a radio button? (marked for real, this time)