Closed Bug 1353293 Opened 7 years ago Closed 7 years ago

Proper extension not appended to filename in save dialog for images (macOS)

Categories

(Core :: Widget: Cocoa, defect)

52 Branch
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 1321321

People

(Reporter: reddoghud, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170323105023

Steps to reproduce:

Right-click on an image and choose save.  In the ensuing dialog, the extension is not appended to the filename in the filename entry box.  In addition, depending on the image being saved, the "file format" dropdown near the bottom of the dialog may say "Preview Document," ".jpg; .jpg; .jpg" or occasionally ".png; .jpg; .jpeg". It's like the browser can't figure out what kind of image it's saving, even though I can verify the filetype ahead of time by right-clicking the image and hitting "View Image Info."

In general, I'm not a huge fan of the concept of hiding the extension of any file -- not sure if there was a change to enforce that kind of behavior, but somewhere this changed in a recent update, and is different behavior from just about every previous version of firefox I've ever used on macOS.


Actual results:

Firefox saves the image with a default extension, which is often wrong.  For example, it may save a JPG with a PNG extension, or vice-versa.


Expected results:

Firefox should append the appropriate extension to the filename and not attempt to hide/truncate it.
Component: Untriaged → Widget: Cocoa
Product: Firefox → Core
Tristan,

Do you by any chance have your Finder preference (Advanced section) to not show file extensions? That said, I suspect that this is bug 1321321, which is fixed in Firefox 54.
Flags: needinfo?(reddoghud)
Also, please provide a link to an image that gets saved with the wrong file extension.
No, I don't have the preference you talked about enabled as I want to see all of my extensions.

I'll see if I can get a link tonight that recreates it, but the bug you linked to looks to cover the same issue.  Also, thanks for the reminder, looks like I'm a build behind.
(In reply to Tristan Hudson from comment #4)
> I'll see if I can get a link tonight that recreates it, but the bug you
> linked to looks to cover the same issue.

I'm marking this as a duplicate then. The missing extension is a bit weird since I've never seen it myself and it just started to work again for the reporter in bug 1321321. It could be that some OS preference have gotten corrupt or altered in some way (see the discussion in bug 1321321).
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(reddoghud)
Yep, sorry, I was trying to find an image link that would reproduce it but wasn't able to in the past couple of days.  OK with the dupe and I'll open another bug if it happens after I upgrade to build 54.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: